From: Daniel Jacobowitz <drow@false.org>
To: binutils@sources.redhat.com
Subject: Re: [PATCH] inconsistent DWARF2 sections generated by --gdwarf2
Date: Thu, 18 Nov 2004 18:42:00 -0000 [thread overview]
Message-ID: <20041118184149.GA23789@nevyn.them.org> (raw)
In-Reply-To: <419CE636.9090807@tensilica.com>
On Thu, Nov 18, 2004 at 10:13:10AM -0800, Bob Wilson wrote:
> That's irrelevant, though, because the situation in question occurs only
> when there is no debug line info. dwarf2_finish is currently writing an
> (empty) .debug_line section even when there is no line number data. The
> whole point of the patch is to fix that! (Sorry, I guess I didn't make
> that clear earlier.)
Oh, thanks! That wasn't clear.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-18 18:42 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
2004-11-18 18:14 ` Bob Wilson
2004-11-18 18:42 ` Daniel Jacobowitz [this message]
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=20041118184149.GA23789@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@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).