From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: Ron McCall <ronald.mccall@snet.net>, gdb@sources.redhat.com
Subject: Re: warning: (Internal error: pc 0xd00 in read in psymtab, but not in symtab.)
Date: Wed, 16 Nov 2005 02:56:00 -0000 [thread overview]
Message-ID: <20051116025603.GA28168@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0511151854s18acc3aaw8f612c3158089a15@mail.gmail.com>
On Tue, Nov 15, 2005 at 06:54:12PM -0800, Jim Blandy wrote:
> On 11/15/05, Daniel Jacobowitz <drow@false.org> wrote:
> > If you're going to change the toolchain to solve this problem, this
> > isn't the way to do it. Just put the .debug_info section in a COMDAT
> > group with the section to be discarded. This should be a pretty
> > trivial change nowadays, since the linker has grown proper COMDAT
> > support.
>
> Okay. I was hoping to get an answer of the form "Don't bother .* COMDAT .*".
:-)
It's mostly a matter of (A) getting gcc to actually start using comdat
where available, there were some hiccups last time we tried, and (B)
teaching the dwarf writer how to partition debug info; no one really
loves that code...
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-11-16 2:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 15:07 Ron McCall
2005-11-13 17:39 ` Daniel Jacobowitz
2005-11-15 1:07 ` Ron McCall
2005-11-15 2:09 ` Daniel Jacobowitz
2005-11-16 3:28 ` Ron McCall
2005-11-15 6:50 ` Vladimir Prus
2005-11-15 20:46 ` Ron McCall
2005-11-15 23:10 ` Jim Blandy
2005-11-15 23:25 ` Daniel Jacobowitz
2005-11-16 0:12 ` Jim Blandy
2005-11-16 0:38 ` Daniel Jacobowitz
2005-11-16 1:33 ` Jim Blandy
2005-11-16 2:53 ` Daniel Jacobowitz
[not found] ` <20051116025218.GA27921@nevyn.them.org>
2005-11-16 2:54 ` Jim Blandy
2005-11-16 2:56 ` Daniel Jacobowitz [this message]
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=20051116025603.GA28168@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@red-bean.com \
--cc=ronald.mccall@snet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).