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 00:38:00 -0000 [thread overview]
Message-ID: <20051116003812.GA25895@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0511151612g34ce97ccn9a6b5101615b49f5@mail.gmail.com>
On Tue, Nov 15, 2005 at 04:12:14PM -0800, Jim Blandy wrote:
> On 11/15/05, Daniel Jacobowitz <drow@false.org> wrote:
> > No, that doesn't work. The high address is probably
> > .gnu.linkonce.foo+0x104, which may show up as 0x104 depending on the
> > relocation format in use.
>
> Checking my understanding:
>
> When we drop a linkonce section, we also drop all relocs referring to
> symbols defined in that section, or the section's STT_SECTION symbol.
> (Or do we just make the relocs use STN_UNDEF as their symbol?) If the
Neither, quite. We specifically fail to resolve them because they are
in .debug_info; otherwise this would be a fatal error.
> architecture uses RELA relocs, then there's probably a zero sitting in
> the code itself, but if it uses REL, then the addend is in the code,
> so we'll see it when we read the value in GDB.
Yes, that's exactly what I meant.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-16 0:38 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 [this message]
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
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=20051116003812.GA25895@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).