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]
Other format:	[Raw text]

Re: cannot allocate memory in static TLS block

From: Jakub Jelinek <jakub at redhat dot com>
To: Thorsten Kukuk <kukuk at suse dot de>
Cc: libc-hacker at sources dot redhat dot com
Date: Fri, 5 Sep 2003 08:14:51 +0200
Subject: Re: cannot allocate memory in static TLS block
References: <20030905060224.GA22568@suse.de>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Fri, Sep 05, 2003 at 08:02:24AM +0200, Thorsten Kukuk wrote:
> 
> Hi,
> 
> compiling the appended test case on i686, gives me the following
> error messages in some configurations:
> 
> # ./dlopen-tls 
> dlopen() failed: './tls.so: cannot allocate memory in static TLS block'
> 
> It does not work with glibc compiled for i686 with TLS and
> without NPTL (the fallback, if somebody uses an older kernel or
> LD_ASSUME_KERNEL=2.4.1).
> 
> Is this a binutils/gcc problem or a bug in glibc? It seems to work
> on other architectures with the same tool chain (gcc 3.3.1, 
> binutils-2.14.90.0.5).

It works for me with all 3 libc/libpthread combos we have on i686
(linuxthreads non-FLOATING_STACKS TLS, non-__thread,
linuxthreads FLOATING_STACKS TLS, non-__thread,
NPTL (obviously TLS __thread), aka LD_ASSUME_KERNEL={2.2.5,2.4.1,2.4.20}),
about a day old CVS checkout.

	Jakub

References:
- cannot allocate memory in static TLS block
  - From: Thorsten Kukuk

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