From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] delete xfail from gdb.base/corefile.exp
Date: Thu, 25 Sep 2003 00:50:00 -0000 [thread overview]
Message-ID: <20030925004943.GA6134@nevyn.them.org> (raw)
In-Reply-To: <yf2y8wd3d9z.fsf@hawaii.kealia.com>
On Wed, Sep 24, 2003 at 05:47:04PM -0700, David Carlton wrote:
> Ever since Jim got corefile.exp working on Linux, I've been annoyed by
> this:
>
> XPASS: gdb.base/corefile.exp: up in corefile.exp (reinit) (PRMS CLLbs17002)
>
> The test passes reliably, and the message refers to some ancient
> bug-tracking system; the easiest solution to me is to just yank the
> setup_xfail. It's possible that the test in question fails on other
> systems; the setup_xfail doesn't give me any reason to believe that
> that is the case.
>
> Tested on i686-pc-linux-gnu, GCC 3.2, both DWARF-2 and stabs. OK to
> commit?
Please do, in fact.
> 2003-09-24 David Carlton <carlton@kealia.com>
>
> * gdb.base/corefile.exp: Delete obsolete setup_xfail.
>
> Index: corefile.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/corefile.exp,v
> retrieving revision 1.7
> diff -u -p -r1.7 corefile.exp
> --- corefile.exp 29 May 2003 23:00:02 -0000 1.7
> +++ corefile.exp 25 Sep 2003 00:43:27 -0000
> @@ -244,7 +244,6 @@ gdb_expect {
> # test reinit_frame_cache
>
> gdb_load ${binfile}
> -setup_xfail "*-*-*" CLLbs17002
> gdb_test "up" "#\[0-9\]* *\[0-9xa-fH'\]* in .* \\(\\).*" "up in corefile.exp (reinit)"
>
> gdb_test "core" "No core file now."
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-09-25 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 0:47 David Carlton
2003-09-25 0:50 ` Daniel Jacobowitz [this message]
2003-09-25 1:36 ` Andrew Cagney
2003-09-25 15:41 ` David Carlton
2003-09-25 0:50 Michael Elizabeth Chastain
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=20030925004943.GA6134@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
/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