Project

General

Profile

Actions

Bug #2663

closed

Strange behaviour when loading a library twice.

Added by shamaz over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Hello. This is an output of uname:

$ uname -a
DragonFly cyberspace.cyberspace 3.6-RELEASE DragonFly
v3.6.2.2.g063e0-RELEASE #7: Sun Apr 13 09:50:36 MSK 2014
:/usr/obj/usr/src/sys/MYKERNEL
x86_64

Trying to port common lisp IOLib library on DragonFly, I have encountered a
strange behaviour (of RTLD as I think). Assume you have a library which
mmap's a fixed (with flag MAP_TRYFIXED) region of memory in its
constructor. When your program opens it with dlopen, then closes it with
dlcose and again opens with dlopen, the second call to mmap from the
constructor will fail. Is it OK?

I attach a testing program (test.c). Try to compile it and run with
libthread_xu.so:

$ cc -o test test.c
$ ./test /usr/lib/thread/libthread_xu.so.

You will get the following output:

testing /usr/lib/thread/libthread_xu.so
Fatal error 'Cannot allocate red zone for initial thread' at line 275 in
file /usr/src/lib/libthread_xu/thread/thr_in
it.c (errno =
12)

Abort (core dumped)

You can try any other library which is linked against -lpthread or you can
try my own library testlib.c
Compile it as follows:

$ cc -shared -fPIC -o testlib.so testlib.c

And run the test:

$ ./test ./testlib.so

You will get:

testing ./libtest.so
0
mmap OK
0
Failed to allocate some space with initialized == 0

In FreeBSD, for example, mmap succeeds two times.


Files

test.c (462 Bytes) test.c shamaz, 04/15/2014 09:07 AM
testlib.c (503 Bytes) testlib.c shamaz, 04/15/2014 09:07 AM
Actions

Also available in: Atom PDF