From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sourceware.org
Subject: Testsuite failures in gdb.base/callfuncs.exp
Date: Wed, 31 Jan 2007 12:33:00 -0000 [thread overview]
Message-ID: <jebqkf9y09.fsf@sykes.suse.de> (raw)
This fixes these testsuite failures on ia64:
FAIL: gdb.base/callfuncs.exp: gdb function calls preserve register contents
FAIL: gdb.base/callfuncs.exp: continue after stop in call dummy preserves register contents
FAIL: gdb.base/callfuncs.exp: return after stop in call dummy preserves register contents
The problem is that the bspstore register is specially tied with the bsp
register, and this can't be controlled by gdb.
Andreas.
2007-01-31 Andreas Schwab <schwab@suse.de>
* gdb.base/callfuncs.exp (do_get_all_registers): Filter out
bspstore register on ia64.
--- gdb/testsuite/gdb.base/callfuncs.exp.~1.18.~ 2007-01-10 11:18:57.000000000 +0100
+++ gdb/testsuite/gdb.base/callfuncs.exp 2007-01-31 13:28:38.000000000 +0100
@@ -248,6 +248,11 @@ proc do_get_all_registers { } {
gdb_expect {
-re "info all-registers\r\n(.*)$gdb_prompt $" {
set all_registers_content $expect_out(1,string)
+ if [istarget "ia64-*-*"] {
+ # Filter out bspstore which is specially tied to bsp,
+ # giving spurious differences.
+ regsub {\nbspstore[^\n]*\n} $all_registers_content "\n" all_registers_content
+ }
}
default {}
}
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2007-01-31 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 12:33 Andreas Schwab [this message]
2007-01-31 12:49 ` Daniel Jacobowitz
2007-01-31 13:56 ` Andreas Schwab
2007-01-31 14:15 ` Daniel Jacobowitz
2007-01-31 14:57 ` Andreas Schwab
2007-01-31 15:10 ` Daniel Jacobowitz
2007-01-31 15:35 ` Andreas Schwab
2007-01-31 15:40 ` Daniel Jacobowitz
2007-02-01 22:53 ` Mark Kettenis
2007-02-01 23:29 ` Andreas Schwab
2007-02-08 17:03 ` Daniel Jacobowitz
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=jebqkf9y09.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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