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]

cannot allocate memory in static TLS block

From: Thorsten Kukuk <kukuk at suse dot de>
To: libc-hacker at sources dot redhat dot com
Date: Fri, 5 Sep 2003 08:02:24 +0200
Subject: cannot allocate memory in static TLS block
Organization: SuSE Linux AG, Nuernberg, Germany

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).

 Thanks,
  Thorsten

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE Linux AG        Deutschherrnstr. 15-19        D-90429 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

Attachment: Makefile
Description: Text document

Attachment: dlopen-tls.c
Description: Text document

Attachment: tls.c
Description: Text document

Follow-Ups:
- Re: cannot allocate memory in static TLS block
  - From: Jakub Jelinek

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