From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PING][PATCH][gdb/testsuite] Fix FAILs in gdb.mi/mi-breakpoint-changed.exp
Date: Fri, 22 Oct 2021 08:51:56 +0200 [thread overview]
Message-ID: <e5e17a27-0e67-53f5-f00e-43be6f3a282f@suse.de> (raw)
In-Reply-To: <20211005144645.GA29297@delia>
On 10/5/21 4:46 PM, Tom de Vries wrote:
> Hi,
>
> Since commit e36788d1354 "[gdb/testsuite] Fix handling of nr_args < 3 in
> mi_gdb_test" we run into:
> ...
> PASS: gdb.mi/mi-breakpoint-changed.exp: test_auto_disable: mi runto main
> Expecting: ^(-break-insert -f pendfunc1[^M
> ]+)?((&.*)*.*~"Breakpoint 2 at.*\\n".*=breakpoint-created,\
> bkpt=\{number="2",type="breakpoint".*\}.*\n\^done[^M
> ]+[(]gdb[)] ^M
> [ ]*)
> -break-insert -f pendfunc1^M
> ^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",\
> addr="0x00007ffff7bd559e",func="pendfunc1",\
> file="gdb/testsuite/gdb.mi/pendshr1.c",\
> fullname="gdb/testsuite/gdb.mi/pendshr1.c",line="21",thread-groups=["i1"],\
> times="0",original-location="pendfunc1"}^M
> (gdb) ^M
> FAIL: gdb.mi/mi-breakpoint-changed.exp: test_auto_disable: \
> -break-insert -f pendfunc1 (unexpected output)
> ...
>
> The regexp expects a breakpoint-created event, but that's actually suppressed
> by the command:
> ...
> DEF_MI_CMD_MI_1 ("break-insert", mi_cmd_break_insert,
> &mi_suppress_notification.breakpoint),
> ...
>
> Fix this by updating the regexp.
>
> Likewise for the following:
> ...
> PASS: gdb.mi/mi-breakpoint-changed.exp: test_auto_disable: \
> -break-insert -f pendfunc1
> Expecting: ^(-break-enable count 1 2[^M
> ]+)?(=breakpoint-modified,\
> bkpt=\{number="2",type="breakpoint",disp="dis",enabled="y".*\}.*\n\^done[^M
> ]+[(]gdb[)] ^M
> [ ]*)
> -break-enable count 1 2^M
> ^done^M
> (gdb) ^M
> FAIL: gdb.mi/mi-breakpoint-changed.exp: test_auto_disable: \
> -break-enable count 1 2 (unexpected out\
> put)
> ...
>
> Tested on x86_64-linux.
>
> Any comments?
>
Ping.
Thanks,
- Tom
> [gdb/testsuite] Fix FAILs in gdb.mi/mi-breakpoint-changed.exp
>
> ---
> gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp b/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp
> index d068a25b9f4..4376bb883e6 100644
> --- a/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp
> +++ b/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp
> @@ -273,11 +273,11 @@ proc test_auto_disable { } {
>
> # Set the breakpoint.
> mi_gdb_test "-break-insert -f pendfunc1" \
> - {(&.*)*.*~"Breakpoint 2 at.*\\n".*=breakpoint-created,bkpt=\{number="2",type="breakpoint".*\}.*\n\^done}
> + {\^done,bkpt=\{number="2",type="breakpoint".*\}.*}
>
> # Enable for one shot only.
> mi_gdb_test "-break-enable count 1 2" \
> - {=breakpoint-modified,bkpt=\{number="2",type="breakpoint",disp="dis",enabled="y".*\}.*\n\^done}
> + {\^done}
>
> mi_send_resuming_command "exec-continue" "continuing execution to breakpoint"
>
>
next prev parent reply other threads:[~2021-10-22 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 14:46 [PATCH][gdb/testsuite] " Tom de Vries via Gdb-patches
2021-10-22 6:51 ` Tom de Vries via Gdb-patches [this message]
2021-10-22 12:55 ` Simon Marchi via Gdb-patches
2021-10-22 15:43 ` Tom de Vries via Gdb-patches
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=e5e17a27-0e67-53f5-f00e-43be6f3a282f@suse.de \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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