From: John Williams <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:35:00 -0000 [thread overview]
Message-ID: <3F3C1EE9.5070802@itee.uq.edu.au> (raw)
In-Reply-To: <1060903735.1578.33.camel@lindt.uglyboxes.com>
Keith Seitz wrote:
> On Thu, 2003-08-14 at 15:01, John Williams wrote:
>
>>>- "list ext2_read_super": Does it return the correct source?
>>
>>Nope - it lists the "correct" line numbers from the wrong file. I'm
>>guessing this is a problem in the binutils addr2line, is that what it's for?
>
>
> Close. Binutils doesn't really read debug info the way gdb does. They
> both try to do the same thing, but gdb looks at it slightly differently.
OK.
>>I'm not too stressed about this, I can just rename the source file and
>>rebuild the project as I need to, just wanted to know if there was
>>something simple I might do.
>
> Yeah -- that's been the sad approach used by most. As I recall we have a
> file in gdb that used to use the same filename as another file in bfd.
> Instead fixing gdb, someone renamed gdb's file!
ha! well if it's good enough for gdb, it's good enough for me :)
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?
Thanks,
John
next prev parent reply other threads:[~2003-08-14 23:35 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 [this message]
2003-08-14 23:42 ` Keith Seitz
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=3F3C1EE9.5070802@itee.uq.edu.au \
--to=jwilliams@itee.uq.edu.au \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).