From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 09/14] gdb/testsuite/gdb.base/break.exp: split test_break_silent_and_more
Date: Wed, 23 Nov 2022 13:39:54 -0500 [thread overview]
Message-ID: <20221123183959.2476477-10-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20221123183959.2476477-1-simon.marchi@polymtl.ca>
This one is a bit tricky. The clear tests seem to depend on the various
breakpoints that have been set before, starting with the "silent"
breakpoints. So, move all this in a single chunk, it can always be
split later if needed.
Change-Id: I7ba61a5b130ade63eda0c4790534840339f8a72f
---
gdb/testsuite/gdb.base/break.exp | 118 ++++++++++++++++---------------
1 file changed, 62 insertions(+), 56 deletions(-)
diff --git a/gdb/testsuite/gdb.base/break.exp b/gdb/testsuite/gdb.base/break.exp
index cc327c195f46..e8762ffa664c 100644
--- a/gdb/testsuite/gdb.base/break.exp
+++ b/gdb/testsuite/gdb.base/break.exp
@@ -533,75 +533,81 @@ gdb_test "break if (1)" \
# Verify that a "silent" breakpoint can be set, and that GDB is indeed
# "silent" about its triggering.
-#
-if ![runto_main] then {
- return
-}
-gdb_test_multiple "break $bp_location1" \
- "set to-be-silent break bp_location1" {
- -re "Breakpoint (\[0-9\]*) at .*, line $bp_location1.*$gdb_prompt $" {
- set bpno $expect_out(1,string)
- pass "set to-be-silent break bp_location1"
- }
+proc_with_prefix test_break_silent_and_more {} {
+ clean_restart break
+
+ if ![runto_main] then {
+ return
}
-gdb_test "commands $bpno\nsilent\nend" ">end" "set silent break bp_location1"
+ gdb_test_multiple "break $::bp_location1" \
+ "set to-be-silent break bp_location1" {
+ -re "Breakpoint (\[0-9\]*) at .*, line $::bp_location1.*$::gdb_prompt $" {
+ set bpno $expect_out(1,string)
+ pass "set to-be-silent break bp_location1"
+ }
+ }
-gdb_test "info break $bpno" \
- "\[0-9\]*\[ \t\]*breakpoint.*:$bp_location1\r\n\[ \t\]*silent.*" \
- "info silent break bp_location1"
+ gdb_test "commands $bpno\nsilent\nend" ">end" "set silent break bp_location1"
-gdb_test "continue" "Continuing." \
- "hit silent break bp_location1"
+ gdb_test "info break $bpno" \
+ "\[0-9\]*\[ \t\]*breakpoint.*:$::bp_location1\r\n\[ \t\]*silent.*" \
+ "info silent break bp_location1"
-gdb_test "bt" "#0 main .* at .*:$bp_location1.*" \
- "stopped for silent break bp_location1"
+ gdb_test "continue" "Continuing." \
+ "hit silent break bp_location1"
-# Verify the $_hit_bpnum convenience variable is set to the silent hit bpno.
-gdb_test "printf \"%d\\n\", \$_hit_bpnum" "$bpno" \
- "Silent breakpoint hit \$_hit_bpnum is silent $bpno"
-
-# Verify that GDB can at least parse a breakpoint with the
-# "thread" keyword. (We won't attempt to test here that a
-# thread-specific breakpoint really triggers appropriately.
-# The gdb.threads subdirectory contains tests for that.)
-#
-set bp_location12 [gdb_get_line_number "set breakpoint 12 here"]
-gdb_test "break $bp_location12 thread 999" "Unknown thread 999.*" \
- "thread-specific breakpoint on non-existent thread disallowed"
+ gdb_test "bt" "#0 main .* at .*:$::bp_location1.*" \
+ "stopped for silent break bp_location1"
-gdb_test "break $bp_location12 thread foo" \
- "Invalid thread ID: foo" \
- "thread-specific breakpoint on bogus thread ID disallowed"
+ # Verify the $_hit_bpnum convenience variable is set to the silent hit bpno.
+ gdb_test "printf \"%d\\n\", \$_hit_bpnum" "$bpno" \
+ "Silent breakpoint hit \$_hit_bpnum is silent $bpno"
-# Verify that GDB responds gracefully to a breakpoint command with
-# trailing garbage.
-#
-gdb_test "break $bp_location12 foo" \
- "malformed linespec error: unexpected string, \"foo\".*" \
- "breakpoint with trailing garbage disallowed"
+ # Verify that GDB can at least parse a breakpoint with the
+ # "thread" keyword. (We won't attempt to test here that a
+ # thread-specific breakpoint really triggers appropriately.
+ # The gdb.threads subdirectory contains tests for that.)
+ #
+ set bp_location12 [gdb_get_line_number "set breakpoint 12 here"]
+ gdb_test "break $bp_location12 thread 999" "Unknown thread 999.*" \
+ "thread-specific breakpoint on non-existent thread disallowed"
-# Verify that GDB responds gracefully to a "clear" command that has
-# no matching breakpoint. (First, get us off the current source line,
-# which we know has a breakpoint.)
-#
-gdb_test "next" "marker1.*" "step over breakpoint"
+ gdb_test "break $bp_location12 thread foo" \
+ "Invalid thread ID: foo" \
+ "thread-specific breakpoint on bogus thread ID disallowed"
-gdb_test "clear 81" "No breakpoint at 81.*" \
- "clear line has no breakpoint disallowed"
+ # Verify that GDB responds gracefully to a breakpoint command with
+ # trailing garbage.
+ #
+ gdb_test "break $bp_location12 foo" \
+ "malformed linespec error: unexpected string, \"foo\".*" \
+ "breakpoint with trailing garbage disallowed"
-gdb_test "clear" "No breakpoint at this line.*" \
- "clear current line has no breakpoint disallowed"
+ # Verify that GDB responds gracefully to a "clear" command that has
+ # no matching breakpoint. (First, get us off the current source line,
+ # which we know has a breakpoint.)
+ #
+ gdb_test "next" "marker1.*" "step over breakpoint"
-# Verify that we can set and clear multiple breakpoints.
-#
-# We don't test that it deletes the correct breakpoints. We do at
-# least test that it deletes more than one breakpoint.
-#
-gdb_test "break marker3" "Breakpoint.*at.*" "break marker3 #1"
-gdb_test "break marker3" "Breakpoint.*at.*" "break marker3 #2"
-gdb_test "clear marker3" {Deleted breakpoints [0-9]+ [0-9]+.*}
+ gdb_test "clear 81" "No breakpoint at 81.*" \
+ "clear line has no breakpoint disallowed"
+
+ gdb_test "clear" "No breakpoint at this line.*" \
+ "clear current line has no breakpoint disallowed"
+
+ # Verify that we can set and clear multiple breakpoints.
+ #
+ # We don't test that it deletes the correct breakpoints. We do at
+ # least test that it deletes more than one breakpoint.
+ #
+ gdb_test "break marker3" "Breakpoint.*at.*" "break marker3 #1"
+ gdb_test "break marker3" "Breakpoint.*at.*" "break marker3 #2"
+ gdb_test "clear marker3" {Deleted breakpoints [0-9]+ [0-9]+.*}
+}
+
+test_break_silent_and_more
# Verify that a breakpoint can be set via a convenience variable.
--
2.38.1
next prev parent reply other threads:[~2022-11-23 18:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 18:39 [PATCH 00/14] Break up gdb.base/break.exp in multiple procs Simon Marchi
2022-11-23 18:39 ` [PATCH 01/14] gdb/testsuite/gdb.base/break.exp: split test_break_commands_clear Simon Marchi
2022-11-23 18:39 ` [PATCH 02/14] gdb/testsuite/gdb.base/break.exp: split test_break_file_line_convenience_var Simon Marchi
2022-11-23 18:39 ` [PATCH 03/14] gdb/testsuite/gdb.base/break.exp: split test_rbreak_shlib Simon Marchi
2022-11-23 18:39 ` [PATCH 04/14] gdb/testsuite/gdb.base/break.exp: split test_break_optimized_prologue Simon Marchi
2022-11-23 18:39 ` [PATCH 05/14] gdb/testsuite/gdb.base/break.exp: use proc_with_prefix for test_next_with_recursion Simon Marchi
2022-11-23 18:39 ` [PATCH 06/14] gdb/testsuite/gdb.base/break.exp: split test_finish_arguments Simon Marchi
2022-11-23 18:39 ` [PATCH 07/14] gdb/testsuite/gdb.base/break.exp: split test_break_user_call Simon Marchi
2022-11-23 18:39 ` [PATCH 08/14] gdb/testsuite/gdb.base/break.exp: split test_break_line_convenience_var Simon Marchi
2022-11-23 18:39 ` Simon Marchi [this message]
2022-11-23 18:39 ` [PATCH 10/14] gdb/testsuite/gdb.base/break.exp: split test_break_default Simon Marchi
2022-11-23 18:39 ` [PATCH 11/14] gdb/testsuite/gdb.base/break.exp: split test_break_nonexistent_line Simon Marchi
2022-11-23 18:39 ` [PATCH 12/14] gdb/testsuite/gdb.base/break.exp: split test_no_break_on_catchpoint Simon Marchi
2022-11-23 18:39 ` [PATCH 13/14] gdb/testsuite/gdb.base/break.exp: split test_tbreak Simon Marchi
2022-11-23 18:39 ` [PATCH 14/14] gdb/testsuite/gdb.base/break.exp: split test_break Simon Marchi
2022-11-24 3:03 ` [PATCH 00/14] Break up gdb.base/break.exp in multiple procs Kevin Buettner
2022-11-24 15:14 ` Simon Marchi
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=20221123183959.2476477-10-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).