gdb.trace: Fix another expected message on continue.
Commit Message
Missed one message in bd0a71fa16f668341a9361c695bc3ca44d27b322, since it
didn't trigger on s390x or amd64 (fast tracepoint out of range due to
shared library usage), noticed on s390.
Pushed as obvious.
gdb/testsuite/ChangeLog:
* gdb.trace/pending.exp: Fix expected message on continue.
---
gdb/gdbserver/ChangeLog | 4 ++++
gdb/testsuite/gdb.trace/pending.exp | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
Comments
@@ -1,3 +1,7 @@
+2016-01-23 Marcin Kościelnicki <koriakin@0x04.net>
+
+ * gdb.trace/pending.exp: Fix expected message on continue.
+
2016-01-22 Marcin Kościelnicki <koriakin@0x04.net>
* tracepoint.c (write_inferior_data_ptr): Cast to uintptr_t, so that
@@ -221,7 +221,7 @@ proc pending_tracepoint_resolved_during_trace { trace_type } \
fail $test
}
}
- -re "Continuing.\r\n(Reading .* from remote target...\r\n)?\r\nBreakpoint.*marker.*at.*$srcfile.*$gdb_prompt $" {
+ -re "Continuing.\r\n(Reading .* from remote target...\r\n)?\r\n(Thread .* hit )?Breakpoint.*marker.*at.*$srcfile.*$gdb_prompt $" {
pass $test
}
}