This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: libc/1818: pthread problem with dlcose()

To: Ulrich Drepper <drepper at cygnus dot com>
Subject: Re: libc/1818: pthread problem with dlcose()
From: "H . J . Lu" <hjl at lucon dot org>
Date: Tue, 18 Jul 2000 17:31:56 -0700
Cc: Mark Kettenis <kettenis at wins dot uva dot nl>,libc-hacker at sourceware dot cygnus dot com
References: <200007190007.e6J07gm14827@delius.kettenis.local> <m3r98r0y8e.fsf@otr.mynet.cygnus.com>

On Tue, Jul 18, 2000 at 05:17:53PM -0700, Ulrich Drepper wrote:
> 
> This would be an ugly hack which pollutes the otherwise quite clean
> code.  And I don't think it's worth it.  Applications which are using
> thread, possibly through modules, should be linked against the thread
> library.
> 
> Solaris solves the problem (they also don't allow unloading the thread
> library) is by having the flag DF_1_NODELETE set in the FLAGS_1 word
> of the thread library.  This is a much more worthwhile way to handle
> this.

I can look into implmenting it in the linker.


H.J.

References:
- Re: libc/1818: pthread problem with dlcose()
  - From: Mark Kettenis
- Re: libc/1818: pthread problem with dlcose()
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]