Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3] of [PATCH v2 42/47] gdb_test_multiple: Anchor prompt match if -lbl
Date: Fri, 6 Jun 2025 11:58:05 +0200	[thread overview]
Message-ID: <e6673864-44b9-419c-b0a3-22ea0bd7f466@suse.de> (raw)
In-Reply-To: <868c00ee-c6cd-44fd-89ea-42916ba931c4@palves.net>

On 6/5/25 19:20, Pedro Alves wrote:
> On 2025-06-05 17:37, Pedro Alves wrote:
>> Reading back, I realized that this example looks a bit silly as is, because you could fix it by
>> just moving the "prefix " case earlier than the "prefix foo/bar" cases.  I should make the command output
>> something after "prefix", like "prefix xxx", and then the regexp should match something like:
>>
>>      -re "^\r\nprefix [^\r\n]*(?=\r\n)" {
>>
>> That's more like what the original testcase that exposed the issue does.
>>
>> I'll send an updated patch soon.
> 
> Here it is.
> 

Hi Pedro,

[ FWIW, the way this patch is posted doesn't work well with patchwork:
...
$ git-pw patch apply 113744
Failed to apply patch:
Applying: of [PATCH v2 42/47] gdb_test_multiple: Anchor prompt match if -lbl
error: No valid patches in input (allow with "--allow-empty")
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 of [PATCH v2 42/47] gdb_test_multiple: Anchor 
prompt match if -lbl
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

$ git am --show-current-patch=diff
--- 8< ---
$
...

I managed to apply it by saving the email in thunderbird and using git 
am, though that drops the commit message. ]

> --- 8< ---
>  From 93ce02b9ad0aefefc5f71b6c5d23f565f3f2e87a Mon Sep 17 00:00:00 2001
> From: Pedro Alves <pedro@palves.net>
> Date: Thu, 5 Jun 2025 18:09:44 +0100
> Subject: [PATCH] gdb_test_multiple: Anchor prompt match if -lbl
> 
> The testcase added by this patch has a gdb_test_multiple call that
> wants to match different lines of output that all have a common
> prefix, and do different actions on each.  Instead of a single regular
> expression with alternatives, its clearer code if the different

its -> it's

> expressions are handled with different "-re", like so:
> 
>    gdb_test_multiple "command" "" -lbl {
>       -re "^command(?=\r\n)" {
> 	 exp_continue
>       }
>       -re "^\r\nprefix foo(?=\r\n)" {
> 	 # Some action for "foo".
> 	 exp_continue
>       }
>       -re "^\r\nprefix bar(?=\r\n)" {
> 	 # Some action for "bar".
> 	 exp_continue
>       }
>       -re "^\r\nprefix \[^\r\n\]*(?=\r\n)" {
> 	 # Some action for all others.
> 	 exp_continue
>       }
>       -re "^\r\n$::gdb_prompt $" {
> 	 gdb_assert {$all_prefixes_were_seen} $gdb_test_name
>       }
>    }
> 
> Above, the leading anchors in the "^\r\nprefix..." matches are needed
> to avoid too-eager matching due to the common prefix.  Without the
> anchors, if the expect output buffer happens to contain at least:
> 
>    "\r\nprefix xxx\r\nprefix foo\r\n"
> 
> ... then the "prefix foo" pattern match inadvertently consumes the
> first "prefix xxx" line.
> 
> Without the anchor in the prompt match, like:
> 
>    -re "\r\n$::gdb_prompt $" {
>        gdb_assert {$all_prefixes_were_seen} $gdb_test_name
>    }
> 
> Or the equivalent:
> 
>    -re -wrap "" {
>        gdb_assert {$all_prefixes_were_seen} $gdb_test_name
>    }
> 
> ... then if the expect buffer contains:
> 
>    "\r\nmeant-to-be-matched-by-lbl\r\nprefix foo\r\n$gdb_prompt "
> 
> ... then the prompt regexp matches this, consuming the "prefix" line
> inadvertently, and we get a FAIL.  The built-in regexp matcher for
> -lbl doesn't get a chance to match the
> "\r\nmeant-to-be-matched-by-lbl\r\n" part, because the built-in prompt
> match appears first within gdb_test_multiple.
> 
> By adding the anchor to the prompt regexp, then we avoid that problem.
> 

Should "then" be dropped in this line?

> However, the same expect output buffer contents will still match the
> built-in prompt match.  That is what is fixed by this patch.  It makes
> it so that if -lbl is specified, the built-in prompt regexp has a
> leading anchor.
> 

Thanks for doing this.

LGTM.

Approved-By: Tom de Vries <tdevries@suse.de>

FWIW, I propose to apply this independently from the patch series, since 
AFAICT it's unrelated.

Thanks,
- Tom

> Original idea for turning this into a gdb.testsuite/ testcase by Tom
> de Vries <tdevries@suse.de>.
> 
> Change-Id: Ic2571ec793d856a89ee0d533ec363e2ac6036ea2
> ---
>   .../gdb.testsuite/gdb_test_multiple-lbl.exp   | 84 +++++++++++++++++++
>   .../gdb.testsuite/gdb_test_multiple-lbl.gdb   | 25 ++++++
>   gdb/testsuite/lib/gdb.exp                     |  4 +-
>   3 files changed, 112 insertions(+), 1 deletion(-)
>   create mode 100644 gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.exp
>   create mode 100755 gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.gdb
> 
> diff --git a/gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.exp b/gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.exp
> new file mode 100644
> index 00000000000..a05ce614b1d
> --- /dev/null
> +++ b/gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.exp
> @@ -0,0 +1,84 @@
> +# Copyright 2025 Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
> +
> +# Test gdb_test_multiple -lbl, particularly with patterns that share a
> +# common prefix.
> +
> +standard_testfile
> +
> +clean_restart
> +
> +gdb_test_no_output "source ${srcdir}/${subdir}/$testfile.gdb" \
> +    "source gdb test script"
> +
> +set saw_prompt 0
> +set saw_prefix 0
> +set saw_command 0
> +set saw_prefix_foo 0
> +set saw_prefix_bar 0
> +
> +# #1 - We need anchors so that the "prefix foo" pattern below does not
> +# match when the expect output buffer contains:
> +#
> +#  "\r\nprefix xxx\r\n\prefix foo\r\n"
> +#
> +# #2 - We need an anchor on the prompt match as otherwise the prompt
> +# regexp would match:
> +#
> +#  "\r\nmeant-to-be-matched-by-lbl-2\r\nprefix xxx\r\n(gdb) "
> +#
> +# This test would fail if -lbl did not force the built-in prompt match
> +# regexp to have an anchor as well, as without it, the built-in prompt
> +# regexp would have the exact same issue as #2 above.
> +
> +gdb_test_multiple "command" "" -lbl {
> +    -re "^command(?=\r\n)" {
> +	verbose -log <COMMAND>
> +	incr saw_command
> +	exp_continue
> +    }
> +    -re "^\r\nprefix foo(?=\r\n)" {
> +	verbose -log <PREFIX-FOO>
> +	incr saw_prefix_foo
> +	exp_continue
> +    }
> +    -re "^\r\nprefix bar(?=\r\n)" {
> +	verbose -log <PREFIX-BAR>
> +	incr saw_prefix_bar
> +	exp_continue
> +    }
> +    -re "^\r\nprefix \[^\r\n\]*(?=\r\n)" {
> +	verbose -log <PREFIX>
> +	incr saw_prefix
> +	exp_continue
> +    }
> +    -re "^\r\n$gdb_prompt $" {
> +	verbose -log <PROMPT>
> +	incr saw_prompt
> +	pass $gdb_test_name
> +    }
> +}
> +
> +verbose -log "saw_command: $saw_command"
> +verbose -log "saw_prefix_foo: $saw_prefix_foo"
> +verbose -log "saw_prefix_bar: $saw_prefix_bar"
> +verbose -log "saw_prefix: $saw_prefix"
> +verbose -log "saw_prompt: $saw_prompt"
> +
> +gdb_assert {$saw_command == 1}
> +gdb_assert {$saw_prefix_foo == 1}
> +gdb_assert {$saw_prefix_bar == 1}
> +gdb_assert {$saw_prefix == 3}
> +gdb_assert {$saw_prompt == 1}
> diff --git a/gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.gdb b/gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.gdb
> new file mode 100755
> index 00000000000..8c94dfa9211
> --- /dev/null
> +++ b/gdb/testsuite/gdb.testsuite/gdb_test_multiple-lbl.gdb
> @@ -0,0 +1,25 @@
> +# Copyright 2025 Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
> +
> +define command
> +  echo prefix xxx\n
> +  echo meant-to-be-matched-by-lbl-1\n
> +  echo prefix foo\n
> +  echo prefix bar\n
> +  echo meant-to-be-matched-by-lbl-2\n
> +  echo prefix xxx\n
> +  echo prefix xxx\n
> +  echo meant-to-be-matched-by-lbl-3\n
> +end
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 0caa9cccd80..eefb6382a27 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -1127,6 +1127,7 @@ proc gdb_test_multiple { command message args } {
>       global any_spawn_id
>   
>       set line_by_line 0
> +    set lbl_anchor_re ""
>       set prompt_regexp ""
>       set prompt_anchor 1
>       for {set i 0} {$i < [llength $args]} {incr i} {
> @@ -1136,6 +1137,7 @@ proc gdb_test_multiple { command message args } {
>   	    set prompt_regexp [lindex $args $i]
>   	} elseif { $arg == "-lbl" } {
>   	    set line_by_line 1
> +	    set lbl_anchor_re "^"
>   	} elseif { $arg == "-no-prompt-anchor" } {
>   	    set prompt_anchor 0
>   	} else {
> @@ -1394,7 +1396,7 @@ proc gdb_test_multiple { command message args } {
>   	    fail "$errmsg"
>   	    set result -1
>   	}
> -	-re "\r\n$prompt_regexp" {
> +	-re "${lbl_anchor_re}\r\n$prompt_regexp" {
>   	    if {![string match "" $message]} {
>   		fail "$message"
>   	    }
> 
> base-commit: f601ffb52199a883f16df385b73a14e756b3e19a


  reply	other threads:[~2025-06-06 10:00 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 13:22 [PATCH v2 00/47] Windows non-stop mode Pedro Alves
2025-05-19 13:22 ` [PATCH v2 01/47] Make default_gdb_exit resilient to failed closes Pedro Alves
2025-05-19 13:56   ` Andrew Burgess
2025-06-06 13:56     ` Pedro Alves
2025-05-19 13:22 ` [PATCH v2 02/47] Add test for continuing with some threads running Pedro Alves
2025-05-21 19:36   ` Kevin Buettner
2026-04-02 13:07     ` Pedro Alves
2025-05-19 13:22 ` [PATCH v2 03/47] infrun: Remove unnecessary currently_stepping call Pedro Alves
2025-05-21 19:44   ` Kevin Buettner
2026-04-02 13:17     ` Pedro Alves
2025-05-19 13:22 ` [PATCH v2 04/47] infrun: Split currently_stepping, fix sw watchpoints issue Pedro Alves
2026-04-02 13:33   ` Pedro Alves
2025-05-19 13:22 ` [PATCH v2 05/47] thread_info::executing+resumed -> thread_info::internal_state Pedro Alves
2026-04-06 18:01   ` Pedro Alves
2025-05-19 13:22 ` [PATCH v2 06/47] Windows gdb: Dead code in windows_nat_target::do_initial_windows_stuff Pedro Alves
2025-05-19 13:22 ` [PATCH v2 07/47] Windows gdb: Eliminate global current_process.dr[8] global Pedro Alves
2025-05-28 19:09   ` Tom Tromey
2026-04-06 19:44   ` Pedro Alves
2025-05-19 13:22 ` [PATCH v2 08/47] Windows gdb+gdbserver: New find_thread, replaces thread_rec(DONT_INVALIDATE_CONTEXT) Pedro Alves
2025-05-19 13:22 ` [PATCH v2 09/47] Windows gdb: handle_output_debug_string return type Pedro Alves
2025-05-19 13:22 ` [PATCH v2 10/47] Windows gdb: Eliminate reload_context Pedro Alves
2025-05-19 13:22 ` [PATCH v2 11/47] Windows gdb+gdbserver: Eliminate thread_rec(INVALIDATE_CONTEXT) calls Pedro Alves
2025-05-19 13:22 ` [PATCH v2 12/47] Windows gdb+gdbserver: Eliminate DONT_SUSPEND Pedro Alves
2025-05-19 13:22 ` [PATCH v2 13/47] Windows gdb+gdbserver: Eliminate windows_process_info::thread_rec Pedro Alves
2025-05-19 13:22 ` [PATCH v2 14/47] Windows gdb: Simplify windows_nat_target::wait Pedro Alves
2025-05-28 19:16   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 15/47] Windows gdb+gdbserver: Move suspending thread to when returning event Pedro Alves
2025-05-28 19:17   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 16/47] Windows gdb: Introduce continue_last_debug_event_main_thread Pedro Alves
2025-05-28 19:18   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 17/47] Windows gdb: Introduce windows_continue_flags Pedro Alves
2025-05-19 13:22 ` [PATCH v2 18/47] Windows gdb: Factor code out of windows_nat_target::windows_continue Pedro Alves
2025-05-19 13:22 ` [PATCH v2 19/47] Windows gdb: Pending stop and current_event Pedro Alves
2025-05-19 13:22 ` [PATCH v2 20/47] Windows gdb+gdbserver: Elim desired_stop_thread_id / rework pending_stops Pedro Alves
2025-05-30 20:41   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 21/47] Windows gdb+gdbserver: Introduce get_last_debug_event_ptid Pedro Alves
2025-05-28 19:21   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 22/47] Windows gdb: Can't pass signal to thread other than last stopped thread Pedro Alves
2025-05-28 19:22   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 23/47] Windows gdbserver: Fix scheduler-locking Pedro Alves
2025-05-30 20:37   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 24/47] Windows gdb: Enable "set scheduler-locking on" Pedro Alves
2025-05-19 13:22 ` [PATCH v2 25/47] Windows gdbserver: Eliminate soft-interrupt mechanism Pedro Alves
2025-05-19 13:22 ` [PATCH v2 26/47] Windows gdb+gdbserver: Make current_event per-thread state Pedro Alves
2025-05-28 19:30   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 27/47] Windows gdb+gdbserver: Make last_sig " Pedro Alves
2025-05-28 19:31   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 28/47] Windows gdb+gdbserver: Make siginfo_er " Pedro Alves
2025-05-28 19:33   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 29/47] Add backpointer from windows_thread_info to windows_process_info Pedro Alves
2025-05-19 13:22 ` [PATCH v2 30/47] Windows gdb+gdbserver: Share $_siginfo reading code Pedro Alves
2025-05-19 13:22 ` [PATCH v2 31/47] Windows gdb+gdbserver: Eliminate struct pending_stop Pedro Alves
2025-05-28 19:36   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 32/47] Windows gdb: Change serial_event management Pedro Alves
2025-05-28 19:37   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 33/47] Windows gdb: cygwin_set_dr => windows_set_dr, etc Pedro Alves
2025-05-19 13:22 ` [PATCH v2 34/47] Windows gdb: Avoid writing debug registers if watchpoint hit pending Pedro Alves
2025-05-30 20:43   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 35/47] Windows gdb+gdbserver: Check whether DBG_REPLY_LATER is available Pedro Alves
2025-05-19 13:22 ` [PATCH v2 36/47] linux-nat: Factor out get_detach_signal code to common code Pedro Alves
2025-05-28 19:44   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 37/47] Windows GDB: make windows_thread_info be private thread_info data Pedro Alves
2025-05-28 19:52   ` Tom Tromey
2025-05-19 13:22 ` [PATCH v2 38/47] Introduce windows_nat::event_code_to_string Pedro Alves
2025-05-28 19:53   ` Tom Tromey
2025-05-19 13:23 ` [PATCH v2 39/47] Windows gdb: Add non-stop support Pedro Alves
2025-06-05 16:21   ` Tom Tromey
2025-05-19 13:23 ` [PATCH v2 40/47] Windows gdb: Eliminate invalidate_context Pedro Alves
2025-05-28 19:54   ` Tom Tromey
2025-05-19 13:23 ` [PATCH v2 41/47] Windows gdb: Watchpoints while running (internal vs external stops) Pedro Alves
2025-05-30 20:50   ` Tom Tromey
2025-05-19 13:23 ` [PATCH v2 42/47] gdb_test_multiple: Anchor prompt match if -lbl Pedro Alves
2025-05-21 15:19   ` Tom de Vries
2025-05-27 22:41     ` Pedro Alves
2025-05-27 23:20       ` Pedro Alves
2025-05-28 11:59         ` [PATCH v2] of " Pedro Alves
2025-06-05 16:37           ` Pedro Alves
2025-06-05 17:20             ` [PATCH v3] " Pedro Alves
2025-06-06  9:58               ` Tom de Vries [this message]
2025-06-06 13:53                 ` Pedro Alves
2025-05-19 13:23 ` [PATCH v2 43/47] Windows gdb: extra thread info => show exiting Pedro Alves
2025-05-28 19:58   ` Tom Tromey
2025-05-19 13:23 ` [PATCH v2 44/47] Add gdb.threads/leader-exit-schedlock.exp Pedro Alves
2025-05-29 16:09   ` Tom Tromey
2025-05-19 13:23 ` [PATCH v2 45/47] infrun: with AS+NS, prefer process exit over thread exit Pedro Alves
2025-05-19 13:23 ` [PATCH v2 46/47] Windows gdb: Always non-stop (default to "maint set target-non-stop on") Pedro Alves
2025-05-29 16:02   ` Tom Tromey
2025-05-19 13:23 ` [PATCH v2 47/47] Mention Windows scheduler-locking and non-stop support in NEWS Pedro Alves
2025-05-19 14:07   ` Eli Zaretskii
2025-06-05 17:57 ` [PATCH v2 00/47] Windows non-stop mode Tom Tromey
2025-06-11 22:06   ` [PATCH] Improve attach on Windows (was: Re: [PATCH v2 00/47] Windows non-stop mode) Pedro Alves
2026-04-02 12:21     ` [PATCH] Improve attach on Windows Pedro Alves
2026-04-02 18:52       ` Tom Tromey
2025-06-11 23:51   ` [PATCH v2 00/47] Windows non-stop mode Pedro Alves
2025-06-12 19:23     ` Tom Tromey
2025-06-13 10:34       ` Pedro Alves
2025-06-13 14:23         ` Tom Tromey

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=e6673864-44b9-419c-b0a3-22ea0bd7f466@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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