From: Corinna Vinschen <vinschen@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Testsuite FAIL which isn't a FAIL in chng-syms.exp
Date: Fri, 27 Feb 2004 12:53:00 -0000 [thread overview]
Message-ID: <20040227125258.GA12904@cygbert.vinschen.de> (raw)
In-Reply-To: <20040226190836.GA32514@nevyn.them.org>
On Feb 26 14:08, Daniel Jacobowitz wrote:
> On Thu, Feb 26, 2004 at 06:07:04PM +0100, Corinna Vinschen wrote:
> > > Not sure what the best fix is. Might work as a hack to add -notransfer
> > > to gdb_run_cmd:
> > >
> > > -notransfer -re "Starting program: \[^\r\n\]*" {}
> >
> > ...this actually fixes it.
> >
> Well, if it works for a native testsuite run (more of the tests run
> that way), then I think it's a plausible change.
I tested once more against Linux and sh-elf target and in the first
case I had no changes in the testsuite results, while in the second
case there's just this FAIL which disappears.
Are you going to submit this to gdb-patches?
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
prev parent reply other threads:[~2004-02-27 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 16:15 Corinna Vinschen
2004-02-26 16:32 ` Daniel Jacobowitz
2004-02-26 17:07 ` Corinna Vinschen
2004-02-26 19:08 ` Daniel Jacobowitz
2004-02-27 12:53 ` Corinna Vinschen [this message]
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=20040227125258.GA12904@cygbert.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb@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