Testsuite fallout from disassemble-next-line

Andreas Schwab
2009-03-29T14:53:12Z

This fixes a spurious failure due to disassemble-next-line. Committed
as obvious.

Andreas.

2009-03-29 Andreas Schwab <schwab@linux-m68k.org>

* gdb.arch/powerpc-prologue.exp: Update for disassemble-next-line.

--- gdb.arch/powerpc-prologue.exp.~1.8.~ 2009-01-03 13:50:36.000000000 +0100
+++ gdb.arch/powerpc-prologue.exp 2009-03-29 16:38:19.000000000 +0200
@@ -50,7 +50,7 @@ if ![runto_main] then {
# Testcase for PIC prologue.

gdb_breakpoint "gdb2029_marker"
-gdb_test "continue" "Breakpoint $decimal, $hex in gdb2029_marker \\(\\)" \
+gdb_test "continue" "Breakpoint $decimal, $hex in gdb2029_marker \\(\\).*" \
"continue to PIC"

gdb_test "backtrace 10" \
@@ -70,7 +70,7 @@ gdb_test "info frame" \
# Testcase for scheduled prologue.

gdb_breakpoint "optimized_1_marker"
-gdb_test "continue" "Breakpoint $decimal, $hex in optimized_1_marker \\(\\)" \
+gdb_test "continue" "Breakpoint $decimal, $hex in optimized_1_marker \\(\\).*" \
"continue to optimized"

gdb_test "backtrace 10" \
No changes between working revision and workfile.

--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."