From: Andreas Schwab <schwab@linux-m68k.org>
To: gdb-patches@sourceware.org
Subject: Testsuite fallout from disassemble-next-line
Date: Sun, 29 Mar 2009 15:39:00 -0000 [thread overview]
Message-ID: <m263hsz8hg.fsf@igel.home> (raw)
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."
reply other threads:[~2009-03-29 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m263hsz8hg.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox