From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Remove all remaining gdb_suppress_entire_file
Date: Fri, 21 Jul 2006 23:28:00 -0000 [thread overview]
Message-ID: <20060721232842.GA30038@nevyn.them.org> (raw)
In-Reply-To: <200607212205.k6LM5sNC003058@elgar.sibelius.xs4all.nl>
On Sat, Jul 22, 2006 at 12:05:54AM +0200, Mark Kettenis wrote:
> > Date: Thu, 20 Jul 2006 17:26:19 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> >
> > Hello,
> >
> > As discussed in the following message:
> >
> > http://www.sourceware.org/ml/gdb-patches/2006-06/msg00347.html
> >
> > The attached patch removes all remaining instances of
> > gdb_suppress_entire_file, and replaces them with a call to untested
> > followed by a return.
>
> Hi Joel,
>
> Most of these are checking compile failures. Are we still seeing some
> sort of ERROR about that in the testsuite output, or just UNTESTED?
gdb_suppress_entire_file used to issue a WARNING. There was never
supposed to be any ERROR - they were caused by cascading failures,
DejaGNU getting confused, and usually the first symptom was a fake
"timeout" while trying to load a file into GDB. And that generated an
ERROR.
After Joel's patch I believe we'll only get an UNTESTED. If you'd
rather we could leave the warning?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-21 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 0:27 Joel Brobecker
2006-07-21 0:43 ` Daniel Jacobowitz
2006-07-21 22:06 ` Mark Kettenis
2006-07-21 22:43 ` Joel Brobecker
2006-07-21 23:28 ` Daniel Jacobowitz [this message]
2006-08-08 19:00 ` Daniel Jacobowitz
2006-08-08 20:10 ` Mark Kettenis
2006-08-08 20:24 ` Daniel Jacobowitz
2006-08-09 18:05 ` Joel Brobecker
2006-08-10 4:13 ` Daniel Jacobowitz
2006-08-10 0:35 ` Daniel Jacobowitz
2006-08-10 14:12 ` Joel Brobecker
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=20060721232842.GA30038@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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