From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sourceware.org
Subject: Fix spurious testsuite failure "up in corefile.exp (reinit)"
Date: Fri, 26 Jan 2007 14:31:00 -0000 [thread overview]
Message-ID: <je64ateu6c.fsf@sykes.suse.de> (raw)
This fixes a spurious testsuite failure on ia64. The full backtrace is
this:
#0 0xa000000000010620 in __kernel_syscall_via_break ()
#1 0x20000000001a3d40 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:67
#2 0x20000000001a6450 in *__GI_abort () at abort.c:88
#3 0x4000000000001020 in func2 () at /cvs/gdb/gdb/testsuite/gdb.base/coremaker.c:127
#4 0x4000000000001060 in func1 () at /cvs/gdb/gdb/testsuite/gdb.base/coremaker.c:133
#5 0x40000000000010e0 in main () at /cvs/gdb/gdb/testsuite/gdb.base/coremaker.c:139
Thus "up" gets you to __GI_raise. The first "up" test already allows a
non-empty arg list.
Andreas.
2007-01-26 Andreas Schwab <schwab@suse.de>
* gdb.base/corefile.exp: Allow non-empty argument list in reinit
test.
--- gdb/testsuite/gdb.base/corefile.exp.~1.11.~ 2007-01-10 11:18:57.000000000 +0100
+++ gdb/testsuite/gdb.base/corefile.exp 2007-01-26 15:24:24.000000000 +0100
@@ -239,6 +239,6 @@ gdb_test_multiple "x/8bd buf2" "$test" {
# test reinit_frame_cache
gdb_load ${binfile}
-gdb_test "up" "#\[0-9\]* *\[0-9xa-fH'\]* in .* \\(\\).*" "up in corefile.exp (reinit)"
+gdb_test "up" "#\[0-9\]* *\[0-9xa-fH'\]* in .* \\(.*\\).*" "up in corefile.exp (reinit)"
gdb_test "core" "No core file now."
--
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-26 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 14:31 Andreas Schwab [this message]
2007-01-26 14:49 ` 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=je64ateu6c.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