From: Fred Fish <fnf@specifix.com>
To: gdb-patches@sourceware.org
Cc: fnf@specifix.com
Subject: [PATCH] Remove XFAIL in interrupt.exp for i*86-pc-linux*-gnu*
Date: Sun, 26 Feb 2006 18:53:00 -0000 [thread overview]
Message-ID: <200602261349.43089.fnf@specifix.com> (raw)
Testing a current development gdb using the current development gcc
produces an XPASS in interrupt.exp. This patch fixes it.
-Fred
2006-02-26 Fred Fish <fnf@specifix.com>
* gdb.base/interrupt.exp: Remove xfail for
"i*86-pc-linux*-gnu*".
Index: testsuite/gdb.base/interrupt.exp
===================================================================
RCS file: /cvsroots/latest/src/gdb/gdb/testsuite/gdb.base/interrupt.exp,v
retrieving revision 1.1.1.1
diff -c -p -r1.1.1.1 interrupt.exp
*** testsuite/gdb.base/interrupt.exp 8 Oct 2005 19:36:19 -0000 1.1.1.1
--- testsuite/gdb.base/interrupt.exp 26 Feb 2006 18:43:31 -0000
*************** if ![file exists $binfile] then {
*** 168,174 ****
eof { fail "echo data (eof)" }
}
- setup_xfail "i*86-pc-linux*-gnu*"
send_gdb "\004"
gdb_expect {
-re "end of file.*Program exited normally.*$gdb_prompt $" {
--- 168,173 ----
next reply other threads:[~2006-02-26 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 18:53 Fred Fish [this message]
2006-02-26 19:11 ` 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=200602261349.43089.fnf@specifix.com \
--to=fnf@specifix.com \
--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