From: Keith Seitz <keiths@redhat.com>
To: jwilliams@itee.uq.edu.au
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: duplicated source file names
Date: Thu, 14 Aug 2003 23:42:00 -0000 [thread overview]
Message-ID: <1060904615.1578.37.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <3F3C1EE9.5070802@itee.uq.edu.au>
On Thu, 2003-08-14 at 16:44, John Williams wrote:
> I have the source of this cross-gdb and can build it myself, if I feel
> inspired one day I might look into it. Recommend any resources (old
> mailing list archives perhaps?) where I might find info on how the bug
> was fixed?
I don't think it's ever been fixed. If it has, it's because of a massive
amount of work going on in the symbol readers and symbol table. You'd
not likely back-patch 5.0 (or event 5.3) with it.
I encourage you to file a bug on it. Heck, make their day: file a bug
and submit a dejagnu testcase for it! This way, there's one more failure
to track.
Keith
next prev parent reply other threads:[~2003-08-14 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 6:59 John Williams
2003-08-14 16:02 ` Keith Seitz
2003-08-14 21:52 ` John Williams
2003-08-14 23:28 ` Keith Seitz
2003-08-14 23:35 ` John Williams
2003-08-14 23:42 ` Keith Seitz [this message]
2003-08-15 15:52 ` Andrew Cagney
2003-08-16 18:46 ` Tom Tromey
2003-08-18 16:03 ` Steve Morgan
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=1060904615.1578.37.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=jwilliams@itee.uq.edu.au \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).