public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Fix step-over-syscall.exp matching regexp for $bpnum.$locno matching Date: Mon, 21 Nov 2022 20:08:50 +0000 (GMT) [thread overview] Message-ID: <20221121200850.46BAF384F6FE@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e66c9edea34ce13e7a6769996e1d151505d8cd3e commit e66c9edea34ce13e7a6769996e1d151505d8cd3e Author: Philippe Waroquiers <philippe.waroquiers@skynet.be> Date: Mon Nov 21 00:14:38 2022 +0100 Fix step-over-syscall.exp matching regexp for $bpnum.$locno matching step-over-syscall.exp has some specific tests for gdbserver. The regexp matching breakpoint hit must take the added locno into account. Test re-run in 3 modes (normal, native-gdbserver and native-extended-gdbserver). Diff: --- gdb/testsuite/gdb.base/step-over-syscall.exp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gdb/testsuite/gdb.base/step-over-syscall.exp b/gdb/testsuite/gdb.base/step-over-syscall.exp index 788f6e3f5d0..530765c3dab 100644 --- a/gdb/testsuite/gdb.base/step-over-syscall.exp +++ b/gdb/testsuite/gdb.base/step-over-syscall.exp @@ -368,12 +368,12 @@ proc break_cond_on_syscall { syscall follow_fork detach_on_fork } { if { $detach_on_fork == "off" } { gdb_test "inferior 1" gdb_test "break marker" "Breakpoint.*at.*" - gdb_test "continue" "Continuing\\..*Breakpoint \[0-9\]+, marker \\(\\) at.*" \ + gdb_test "continue" "Continuing\\..*Breakpoint $::bkptno_numopt_re, marker \\(\\) at.*" \ "continue to marker" } } else { gdb_test "break marker" "Breakpoint.*at.* file .*${testfile}.c, line.*" - gdb_test "continue" "Continuing\\..*Breakpoint \[0-9\]+, marker \\(\\) at.*" \ + gdb_test "continue" "Continuing\\..*Breakpoint $::bkptno_numopt_re, marker \\(\\) at.*" \ "continue to marker" } }
reply other threads:[~2022-11-21 20:08 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221121200850.46BAF384F6FE@sourceware.org \ --to=philippe@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).