gdb/testsuite/gdb.base/break.exp: split test_no_break_on_catchpoint

Change-Id: Ifa7070943f1de22c2839fedf5f346d6591bb5a76
Approved-By: Kevin Buettner <kevinb@redhat.com>
This commit is contained in:
Simon Marchi 2022-11-23 13:39:57 -05:00 committed by Simon Marchi
parent 750375dd69
commit 46c3b224a3

View File

@ -478,21 +478,27 @@ gdb_test "info break" "Num Type.*Disp Enb Address.*What.*\[\r\n\]
# Verify that catchpoints for fork, vfork and exec don't trigger
# inappropriately. (There are no calls to those system functions
# in this test program.)
#
if ![runto_main] then {
return
proc_with_prefix test_no_break_on_catchpoint {} {
clean_restart break
if ![runto_main] then {
return
}
gdb_test "catch fork" "Catchpoint \[0-9\]+ \\(fork\\)" \
"set catch fork, never expected to trigger"
gdb_test "catch vfork" "Catchpoint \[0-9\]+ \\(vfork\\)" \
"set catch vfork, never expected to trigger"
gdb_test "catch exec" "Catchpoint \[0-9\]+ \\(exec\\)" \
"set catch exec, never expected to trigger"
gdb_continue_to_end
}
gdb_test "catch fork" "Catchpoint \[0-9\]+ \\(fork\\)" \
"set catch fork, never expected to trigger"
gdb_test "catch vfork" "Catchpoint \[0-9\]+ \\(vfork\\)" \
"set catch vfork, never expected to trigger"
gdb_test "catch exec" "Catchpoint \[0-9\]+ \\(exec\\)" \
"set catch exec, never expected to trigger"
gdb_continue_to_end
test_no_break_on_catchpoint
# Verify that GDB responds gracefully when asked to set a breakpoint
# on a nonexistent source line.