From: Daniel Jacobowitz <drow@false.org>
To: Nick Clifton <nickc@redhat.com>,
Bob Wilson <bwilson@tensilica.com>,
binutils@sources.redhat.com
Subject: Re: [PATCH] inconsistent DWARF2 sections generated by --gdwarf2
Date: Thu, 18 Nov 2004 14:22:00 -0000 [thread overview]
Message-ID: <20041118142206.GA29928@nevyn.them.org> (raw)
In-Reply-To: <20041118115814.GA22378@bubble.modra.org>
On Thu, Nov 18, 2004 at 10:28:14PM +1030, Alan Modra wrote:
> On Thu, Nov 18, 2004 at 09:22:37AM +0000, Nick Clifton wrote:
> > >But that's the other way around, .debug_info references .debug_line. In
> > >this case we have .debug_line with no .debug_info, which should be OK.
> >
> > Does that make sense though ? A .debug_line compilation unit which does
> > not correspond to any .debug_info compilation unit ? What lines would
> > it be describing ? Why would these lines exist without any debug info ?
>
> .debug_line by itself gives you a mapping between addresses and source
> file line numbers. That might be all a tool needs.
Bob's original mail said it was harmless for GDB - but that's not true.
GDB will only read line number data associated with some compilation
unit.
Is there any reason not to emit a compilation unit, if there isn't one
already, and there is line number data?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-18 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 19:27 Bob Wilson
2004-11-18 3:31 ` Alan Modra
2004-11-18 8:39 ` Nick Clifton
2004-11-18 8:59 ` Alan Modra
2004-11-18 9:18 ` Nick Clifton
2004-11-18 11:58 ` Alan Modra
2004-11-18 14:22 ` Daniel Jacobowitz [this message]
2004-11-18 18:14 ` Bob Wilson
2004-11-18 18:42 ` Daniel Jacobowitz
2004-11-22 12:19 ` Nick Clifton
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=20041118142206.GA29928@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=bwilson@tensilica.com \
--cc=nickc@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).