On some targets each of the assignments "i = 0" in the C source for
"breakpoint-in-ro-region.exp" are compiled to a single instruction.
Then each "si" stops at the beginning of the next source line. But on
some other targets (like s390) such an assignment compiles to multiple
instructions. Then "si" may stop in mid-line, and GDB displays the PC
address in addition to the source line number. This was not considered
by the regexp for this case.
gdb/testsuite/ChangeLog:
* gdb.base/breakpoint-in-ro-region.exp (test_single_step): In the
regexps for GDB's current line display, accept a hex address
preceding the line number.
+2015-03-04 Andreas Arnez <arnez@linux.vnet.ibm.com>
+
+ * gdb.base/breakpoint-in-ro-region.exp (test_single_step): In the
+ regexps for GDB's current line display, accept a hex address
+ preceding the line number.
+
2015-03-04 Andreas Arnez <arnez@linux.vnet.ibm.com>
* gdb.base/catch-syscall.exp (test_catch_syscall_multi_arch): Set
proc test_single_step { always_inserted auto_hw } {
global gdb_prompt
global decimal
+ global hex
global supports_hbreak
global hw_step
gdb_assert {!$hw_step && $auto_hw == "off"} \
"$test (cannot insert sw break)"
}
- -re "^si\r\nNote: automatically using hardware breakpoints for read-only addresses\.\r\n${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
+ -re "^si\r\nNote: automatically using hardware breakpoints for read-only addresses\.\r\n\(\?\:${hex}\[ \t\]\)\?${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
gdb_assert {!$hw_step && $auto_hw == "on" && $supports_hbreak} \
"$test (auto-hw)"
}
- -re "^si\r\n${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
+ -re "^si\r\n\(\?\:${hex}\[ \t\]\)\?${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
gdb_assert {$hw_step || ($auto_hw == "on" && $supports_hbreak)} \
"$test (no error)"
}