From: Guinevere Larsen <blarsen@redhat.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] process-dies-while-detaching.exp: Exit early if GDB misses sync breakpoint
Date: Wed, 4 Oct 2023 12:55:35 +0200 [thread overview]
Message-ID: <82422697-8aa9-d56a-8aa0-2c60703d5276@redhat.com> (raw)
In-Reply-To: <20230929175313.24845-1-thiago.bauermann@linaro.org>
On 29/09/2023 19:53, Thiago Jung Bauermann via Gdb-patches wrote:
> 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.
Thanks for working on this test, it has been driving me up the wall for
a while!
>
> 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.
I like this change, since I didn't actually know that this was TCL's
behavior!
>
> Tested on aarch64-linux.
I tested on x86_64 and I see no regressions.
Tested-By: Guinevere Larsen <blarsen@redhat.com>
I hope this gets approved soon!
--
Cheers,
Guinevere Larsen
She/Her/Hers
> ---
> .../gdb.threads/process-dies-while-detaching.exp | 10 +++++-----
> gdb/testsuite/lib/gdb.exp | 4 ++--
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.threads/process-dies-while-detaching.exp b/gdb/testsuite/gdb.threads/process-dies-while-detaching.exp
> index bbbe82df30cd..c7d43d7dddcc 100644
> --- a/gdb/testsuite/gdb.threads/process-dies-while-detaching.exp
> +++ b/gdb/testsuite/gdb.threads/process-dies-while-detaching.exp
> @@ -127,7 +127,7 @@ proc detach_and_expect_exit {inf_output_re test} {
>
> proc continue_to_exit_bp {} {
> gdb_breakpoint "_exit" temporary
> - gdb_continue_to_breakpoint "_exit" ".*_exit.*"
> + return [gdb_continue_to_breakpoint "_exit" ".*_exit.*"]
> }
>
> # If testing single-process, simply detach from the process.
> @@ -226,7 +226,7 @@ proc test_detach {multi_process cmd} {
> }
>
> # Run to _exit in the child.
> - continue_to_exit_bp
> + return_if_fail [continue_to_exit_bp]
>
> do_detach $multi_process $cmd "normal"
> }
> @@ -265,13 +265,13 @@ proc test_detach_watch {wp multi_process cmd} {
> # them out, and handle the case of the thread disappearing
> # while doing that (on targets that need to detach from each
> # thread individually).
> - continue_to_exit_bp
> + return_if_fail [continue_to_exit_bp]
> } else {
> # Force software watchpoints.
> gdb_test_no_output "set can-use-hw-watchpoints 0"
>
> # As above, but flip order, other wise things take too long.
> - continue_to_exit_bp
> + return_if_fail [continue_to_exit_bp]
> gdb_test "watch globalvar" "Watchpoint $decimal: globalvar"
>
> if { $multi_process == 0 && $cmd == "continue" } {
> @@ -304,7 +304,7 @@ proc test_detach_killed_outside {multi_process cmd} {
> }
>
> # Run to _exit in the child.
> - continue_to_exit_bp
> + return_if_fail [continue_to_exit_bp]
>
> set childpid [get_integer_valueof "mypid" -1]
> if { $childpid == -1 } {
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 1b9179401c45..dfabc99fe4be 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -822,14 +822,14 @@ proc gdb_continue_to_breakpoint {name {location_pattern .*}} {
> set full_name "continue to breakpoint: $name"
>
> set kfail_pattern "Process record does not support instruction 0xfae64 at.*"
> - gdb_test_multiple "continue" $full_name {
> + return [gdb_test_multiple "continue" $full_name {
> -re "(?:Breakpoint|Temporary breakpoint) .* (at|in) $location_pattern\r\n$gdb_prompt $" {
> pass $full_name
> }
> -re "(?:$kfail_pattern)\r\n$gdb_prompt $" {
> kfail "gdb/25038" $full_name
> }
> - }
> + }]
> }
>
>
>
next prev parent reply other threads:[~2023-10-04 10:55 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 [this message]
2023-10-04 22:50 ` Thiago Jung Bauermann
2023-10-06 17:05 ` Andrew Burgess
2023-10-06 20:41 ` Thiago Jung Bauermann
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=82422697-8aa9-d56a-8aa0-2c60703d5276@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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).