mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: Pierre Rousselet <pierre.rousselet@wanadoo.fr>,
	David Ford <david@linux.com>,
	devfs@oss.sgi.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] devfsd, compiling on glibc22x
Date: Mon, 5 Feb 2001 00:01:29 -0700	[thread overview]
Message-ID: <200102050701.f1571TH04804@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <m3lmrl62rm.fsf@otr.mynet.cygnus.com>
In-Reply-To: <3A7383B2.19DDD006@linux.com> <3A73C1D8.578AEEE@wanadoo.fr> <m3wvbgnnk3.fsf@otr.mynet.cygnus.com> <200102050631.f156Vje04234@vindaloo.ras.ucalgary.ca> <m3lmrl62rm.fsf@otr.mynet.cygnus.com>

Ulrich Drepper writes:
> Richard Gooch <rgooch@ras.ucalgary.ca> 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@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-02-05  7:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28  2:28 David Ford
2001-01-28  6:53 ` Pierre Rousselet
2001-01-28  7:27   ` Ulrich Drepper
2001-01-28 10:09     ` David Ford
2001-01-29  2:19     ` Albert D. Cahalan
2001-02-05  6:31   ` Richard Gooch
2001-02-05  6:51     ` Ulrich Drepper
2001-02-05  7:01     ` Richard Gooch [this message]
2001-01-28 15:56 Douglas Gilbert

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=200102050701.f1571TH04804@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=david@linux.com \
    --cc=devfs@oss.sgi.com \
    --cc=drepper@cygnus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.rousselet@wanadoo.fr \
    /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
all inboxes | Powered by JetHome®