From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [ob] Eliminate another gdb_suppress_entire_file
Date: Fri, 23 Jun 2006 03:22:00 -0000 [thread overview]
Message-ID: <20060623032215.GA2754@nevyn.them.org> (raw)
In-Reply-To: <20060623031029.GI976@adacore.com>
On Thu, Jun 22, 2006 at 08:10:29PM -0700, Joel Brobecker wrote:
> > There's a few versions of GCC 4.1 which can't compile gdb.base/store.c. It
> > was eventually fixed on the release branch, but I happen to be testing a
> > version where it's broken. I've been making this change globally as the
> > function in question pops up to bite me.
>
> Should we try to remove all the instances of gdb_suppress_entire_file?
> I don't remember if there are some cases where it's legit to use them.
I'd be in favor.
It's not a bad idea, really. But the way the GDB testsuite is layed
out, I think it's impractical - and I know that in practice it doesn't
work, because it will always provoke an ERROR: Gdb did not load after
10 seconds (or something similar to that).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-23 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 19:58 Daniel Jacobowitz
2006-06-23 3:11 ` Joel Brobecker
2006-06-23 3:22 ` Daniel Jacobowitz [this message]
2006-06-23 3:35 ` Joel Brobecker
2006-06-23 3:40 ` Daniel Jacobowitz
2006-06-23 4:04 ` Joel Brobecker
2006-06-23 12:34 ` 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=20060623032215.GA2754@nevyn.them.org \
--to=drow@false.org \
--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