public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] process-dies-while-detaching.exp: Exit early if GDB misses sync breakpoint
Date: Fri, 06 Oct 2023 17:41:50 -0300	[thread overview]
Message-ID: <87il7jlbzl.fsf@linaro.org> (raw)
In-Reply-To: <87sf6nsmtz.fsf@redhat.com>


Andrew Burgess <aburgess@redhat.com> writes:

> Thiago Jung Bauermann via Gdb-patches <gdb-patches@sourceware.org>
> writes:
>
>> I'm seeing a lot of variability in the failures of
>> gdb.threads/process-dies-while-detaching.exp on aarch64-linux.  On this
>> platform, a problem yet to be investigated causes GDB to miss the _exit
>> breakpoint.  What happens next is random because after missing that
>> breakpoint, GDB is out of sync with the inferior.  This causes the tests
>> following that point in the testcase to fail in a random way.
>>
>> In this scenario it's better to exit the testcase early to avoid random
>> results in the testsuite.
>>
>> We are relying on gdb_continue_to_breakpoint to return the result of
>> gdb_test_multiple.  This is already the case because in Tcl the return
>> value of a function is the return value of the last command it runs.  But
>> change gdb_continue_to_breakpoint to explicitly return this value, to make
>> it clear this is the intended behaviour.
>>
>> Tested on aarch64-linux.
>
> Looks great.  Thanks for improving this.
>
> Approved-By: Andrew Burgess <aburgess@redhat.com>

Thank you! Pushed as commit 0f3efefb34f8.

-- 
Thiago

      reply	other threads:[~2023-10-06 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 17:53 Thiago Jung Bauermann
2023-10-04 10:55 ` Guinevere Larsen
2023-10-04 22:50   ` Thiago Jung Bauermann
2023-10-06 17:05 ` Andrew Burgess
2023-10-06 20:41   ` Thiago Jung Bauermann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87il7jlbzl.fsf@linaro.org \
    --to=thiago.bauermann@linaro.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).