From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randolph Chung To: gdb-patches@sources.redhat.com Subject: [patch/rfa] Allow breakpoing to be added after inferior has started Date: Sat, 22 May 2004 02:31:00 -0000 Message-id: <20040522023133.GG7207@tausq.org> X-SW-Source: 2004-05/msg00657.html The shlib-call.exp test fails on hppa (also ia64) because it tries to add a breakpoint before the inferior is started, so there's no where to put the breakpoint. gdb can handle this case if we allow pending breakpoints in the test. this only works on x86 and some other architectures because they put instructions into the plt; but some architectures put addresses in the plt. ok to commit? randolph 2004-05-21 Randolph Chung * gdb.base/shlib-call.exp: Allow breakpoint to be added after inferior has started. Index: testsuite/gdb.base/shlib-call.exp =================================================================== RCS file: /cvs/src/src/gdb/testsuite/gdb.base/shlib-call.exp,v retrieving revision 1.8 diff -u -p -r1.8 shlib-call.exp --- testsuite/gdb.base/shlib-call.exp 2 Feb 2004 21:14:33 -0000 1.8 +++ testsuite/gdb.base/shlib-call.exp 22 May 2004 02:18:34 -0000 @@ -291,17 +291,17 @@ send_gdb "set width 0\n" ; gdb_expect -r # PR's 16495, 18213 # test that we can re-set breakpoints in shared libraries -gdb_breakpoint "shr1" +gdb_breakpoint "shr1" "allow-pending" # FIXME: should not send "run" explicitly. Non-portable. if ![is_remote target] { - gdb_test "run" "Starting program:.*Breakpoint 1,.*" \ + gdb_test "run" "Starting program:.*Breakpoint .,.*" \ "run to bp in shared library" gdb_test "cont" ".*Program exited normally..*" - gdb_test "run" "Starting program:.*Breakpoint 1,.*" \ + gdb_test "run" "Starting program:.*Breakpoint .,.*" \ "re-run to bp in shared library (PR's 16495, 18213)" gdb_test "cont" ".*Program exited normally..*" -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/