| To: | drepper@xxxxxxxxxx (Ulrich Drepper) |
|---|---|
| Subject: | Re: [PATCH] devfsd, compiling on glibc22x |
| From: | Richard Gooch <rgooch@xxxxxxxxxxxxxxx> |
| Date: | Mon, 5 Feb 2001 00:01:29 -0700 |
| Cc: | Pierre Rousselet <pierre.rousselet@xxxxxxxxxx>, David Ford <david@xxxxxxxxx>, devfs@xxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <m3lmrl62rm.fsf@xxxxxxxxxxxxxxxxxxxx> |
| References: | <3A7383B2.19DDD006@xxxxxxxxx> <3A73C1D8.578AEEE@xxxxxxxxxx> <m3wvbgnnk3.fsf@xxxxxxxxxxxxxxxxxxxx> <200102050631.f156Vje04234@xxxxxxxxxxxxxxxxxxxxxxxx> <m3lmrl62rm.fsf@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-devfs@xxxxxxxxxxx |
Ulrich Drepper writes:
> Richard Gooch <rgooch@xxxxxxxxxxxxxxx> writes:
>
> > So why do old binaries (compiled with glibc 2.1.3) segfault when they
> > call dlsym() with RTLD_NEXT? Even newly compiled binaries (with glibc
> > 2.2) still segfault.
>
> What do you ask me? You wrote the code.
But you wrote dlsym(), right I have a debug trace from someone which
shows that the call to dlsym() segfaults. It's being called thusly:
dlsym (RTLD_NEXT, "symlink");
This doesn't fail with libc 5 nor with glibc 2.1.3. But it does with
glibc 2.2.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] devfsd, compiling on glibc22x, Ulrich Drepper |
|---|---|
| Next by Date: | Re: [PATCH] devfsd, compiling on glibc22x, Mikael Pettersson |
| Previous by Thread: | Re: [PATCH] devfsd, compiling on glibc22x, Ulrich Drepper |
| Next by Thread: | Re: [PATCH] devfsd, compiling on glibc22x, Mikael Pettersson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |