From: "Bradley D. LaRonde" <brad@laronde.org>
To: "Richard Sandiford" <rsandifo@redhat.com>
Cc: <uclibc@uclibc.org>, <linux-mips@linux-mips.org>
Subject: Re: uclibc mips ld.so and undefined symbols with nonzero symbol table entry st_value
Date: Mon, 10 May 2004 16:36:14 -0400 [thread overview]
Message-ID: <01a901c436ce$7029d890$8d01010a@prefect> (raw)
In-Reply-To: 878yg0m9db.fsf@redhat.com
----- Original Message -----
From: "Richard Sandiford" <rsandifo@redhat.com>
To: "Bradley D. LaRonde" <brad@laronde.org>
Cc: <uclibc@uclibc.org>; <linux-mips@linux-mips.org>
Sent: Monday, May 10, 2004 2:21 PM
Subject: Re: uclibc mips ld.so and undefined symbols with nonzero symbol
table entry st_value
> "Bradley D. LaRonde" <brad@laronde.org> writes:
> > Even though it is pointing libdl to the libpthread stub for malloc,
should
> > it crash?
>
> Yeah. When you call a stub, $gp must already be set to the owning
> object's _gp. That's how the dynamic loader knows which GOT to change.
>
> In your case, libdl will be calling libpthread's stub with $gp set to
> libdl's _gp. The dynamic loader will therefore end up trying to change
> libdl's GOT, not libpthread's.
I read this in the spec:
All externally visible symbols, both defined and undefined,
must be hashed into the hash table.
Should libpthread's malloc stub be added to the hash table? I guess not,
but I think that might be happening (haven't verified), and libdl finding it
in there and thinking it is the real deal, not realizing it is just a stub.
Regards,
Brad
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@laronde.org>
To: Richard Sandiford <rsandifo@redhat.com>
Cc: uclibc@uclibc.org, linux-mips@linux-mips.org
Subject: Re: uclibc mips ld.so and undefined symbols with nonzero symbol table entry st_value
Date: Mon, 10 May 2004 16:36:14 -0400 [thread overview]
Message-ID: <01a901c436ce$7029d890$8d01010a@prefect> (raw)
Message-ID: <20040510203614.TLrwhgaLIIu6JFZ259BqednfkQQHZnqXKgOAZZke_TI@z> (raw)
In-Reply-To: 878yg0m9db.fsf@redhat.com
----- Original Message -----
From: "Richard Sandiford" <rsandifo@redhat.com>
To: "Bradley D. LaRonde" <brad@laronde.org>
Cc: <uclibc@uclibc.org>; <linux-mips@linux-mips.org>
Sent: Monday, May 10, 2004 2:21 PM
Subject: Re: uclibc mips ld.so and undefined symbols with nonzero symbol
table entry st_value
> "Bradley D. LaRonde" <brad@laronde.org> writes:
> > Even though it is pointing libdl to the libpthread stub for malloc,
should
> > it crash?
>
> Yeah. When you call a stub, $gp must already be set to the owning
> object's _gp. That's how the dynamic loader knows which GOT to change.
>
> In your case, libdl will be calling libpthread's stub with $gp set to
> libdl's _gp. The dynamic loader will therefore end up trying to change
> libdl's GOT, not libpthread's.
I read this in the spec:
All externally visible symbols, both defined and undefined,
must be hashed into the hash table.
Should libpthread's malloc stub be added to the hash table? I guess not,
but I think that might be happening (haven't verified), and libdl finding it
in there and thinking it is the real deal, not realizing it is just a stub.
Regards,
Brad
next prev parent reply other threads:[~2004-05-10 20:36 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 21:25 uclibc mips ld.so and undefined symbols with nonzero symbol table entry st_value Bradley D. LaRonde
2004-05-03 21:25 ` Bradley D. LaRonde
2004-05-09 13:14 ` Richard Sandiford
2004-05-09 13:14 ` Richard Sandiford
2004-05-09 20:52 ` Bradley D. LaRonde
2004-05-09 20:52 ` Bradley D. LaRonde
2004-05-10 7:40 ` Richard Sandiford
2004-05-10 7:40 ` Richard Sandiford
2004-05-10 18:05 ` Bradley D. LaRonde
2004-05-10 18:05 ` Bradley D. LaRonde
2004-05-10 18:21 ` Richard Sandiford
2004-05-10 18:21 ` Richard Sandiford
2004-05-10 20:36 ` Bradley D. LaRonde [this message]
2004-05-10 20:36 ` Bradley D. LaRonde
2004-05-10 20:41 ` Richard Sandiford
2004-05-10 20:41 ` Richard Sandiford
2004-05-10 20:44 ` Richard Sandiford
2004-05-10 20:44 ` Richard Sandiford
2004-05-11 3:39 ` Bradley D. LaRonde
2004-05-11 3:39 ` Bradley D. LaRonde
2004-05-11 5:48 ` [uClibc] Re: uclibc mips ld.so and undefined symbols with nonzerosymbol " Joakim Tjernlund
2004-05-11 5:48 ` Joakim Tjernlund
2004-05-11 14:03 ` uclibc mips ld.so and undefined symbols with nonzero symbol " Daniel Jacobowitz
2004-05-11 14:21 ` Bradley D. LaRonde
2004-05-11 14:21 ` Bradley D. LaRonde
2004-05-11 14:23 ` Daniel Jacobowitz
2004-05-11 16:33 ` [uClibc] Re: uclibc mips ld.so and undefined symbols with nonzerosymbol " Joakim Tjernlund
2004-05-11 16:33 ` Joakim Tjernlund
2004-05-11 16:55 ` Bradley D. LaRonde
2004-05-11 16:55 ` Bradley D. LaRonde
2004-05-11 21:50 ` Joakim Tjernlund
2004-05-11 21:50 ` Joakim Tjernlund
2004-05-10 12:21 ` Joakim Tjernlund
2004-05-10 12:21 ` Joakim Tjernlund
2004-05-10 12:36 ` Joakim Tjernlund
2004-05-10 12:36 ` Joakim Tjernlund
2004-05-10 14:23 ` Joakim Tjernlund
2004-05-10 14:23 ` Joakim Tjernlund
2004-05-11 7:27 ` [uClibc] Re: uclibc mips ld.so and undefined symbols withnonzerosymbol " Joakim Tjernlund
2004-05-11 7:27 ` Joakim Tjernlund
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='01a901c436ce$7029d890$8d01010a@prefect' \
--to=brad@laronde.org \
--cc=linux-mips@linux-mips.org \
--cc=rsandifo@redhat.com \
--cc=uclibc@uclibc.org \
/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