From: "H. J. Lu" <hjl@lucon.org>
To: Jim Blandy <jimb@redhat.com>,
Steven Johnson <sjohnson@neurizon.net>,
gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: DWARF-2 + discarded link-once sections (was Re: Internal error in GDB)
Date: Wed, 20 Nov 2002 22:30:00 -0000 [thread overview]
Message-ID: <20021120223016.C21917@lucon.org> (raw)
In-Reply-To: <20021121044940.GA20705@nevyn.them.org>; from drow@mvista.com on Wed, Nov 20, 2002 at 11:49:40PM -0500
On Wed, Nov 20, 2002 at 11:49:40PM -0500, Daniel Jacobowitz wrote:
>
> This could work too but it would be nice to avoid it. We were
> discussing .debug_info.gnu.linkonce.* sections at one point; did we
> abandon that idea because there were too many of them, or was there
> some other problem?
What we need is GRP_COMDAT.
H.J.
next prev parent reply other threads:[~2002-11-21 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 23:40 Internal error in GDB Steven Johnson
2002-11-14 7:14 ` Daniel Jacobowitz
2002-11-19 12:09 ` Daniel Jacobowitz
2002-11-20 20:42 ` Jim Blandy
2002-11-20 20:50 ` DWARF-2 + discarded link-once sections (was Re: Internal error in GDB) Daniel Jacobowitz
2002-11-20 22:30 ` H. J. Lu [this message]
2002-11-20 22:40 ` Daniel Berlin
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=20021120223016.C21917@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=sjohnson@neurizon.net \
/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