From: Andreas Schwab <schwab@suse.de>
To: Paul Gilliam <gilliam@us.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: /lib64/ld64.so.1 not being added to target sections list on ppc64
Date: Tue, 06 Feb 2007 09:59:00 -0000 [thread overview]
Message-ID: <jey7nb38ur.fsf@sykes.suse.de> (raw)
In-Reply-To: <OF2F87BDDD.E08F3E42-ON8825727A.00065CB6-8825727A.00088C21@us.ibm.com> (Paul Gilliam's message of "Mon, 5 Feb 2007 17:33:21 -0800")
Paul Gilliam <gilliam@us.ibm.com> writes:
> There is another table of sections that is used when the gdb command 'info
> symbol' is used. If I go:
> (gdb) p &malloc
> (gdb) info symbol $1
>
> gdb responds 'malloc is in the .opd section'
>
> I don't understand:
> 1) why are there two section tables?
> 2) why aren't sections from /lib64/ld64.so.1 being loaded into the target
> sections table?
> 3) why is the function pointer for 'malloc' pointing to a plt in the
> /lib64/ld64.so object and not one in the main executable?
The problem is that there are two malloc implementation, the early one in
ld64.so and the real one in libc.so. Unless you have debugging symbols
for libc.so the real one is never found.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2007-02-06 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 1:33 Paul Gilliam
2007-02-06 1:50 ` Daniel Jacobowitz
2007-02-06 9:59 ` Andreas Schwab [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=jey7nb38ur.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sourceware.org \
--cc=gilliam@us.ibm.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