This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/16592] crash in startup
- From: "stefan at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 18 Feb 2014 04:08:37 +0000
- Subject: [Bug dynamic-link/16592] crash in startup
- Auto-submitted: auto-generated
- References: <bug-16592-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16592
--- Comment #10 from Stefan Seefeld <stefan at codesourcery dot com> ---
Created attachment 7423
--> https://sourceware.org/bugzilla/attachment.cgi?id=7423&action=edit
stacktrace from gdb
The attached stacktrace is seen in gdb when run as
gdb .../ld-2.18.90.so --audit ./ldaudit.so ./probe
The crash happens at
Program received signal SIGSEGV, Segmentation fault.
0x00005555555657a0 in add_to_global (new=new@entry=0x7ffff78509f0) at
dl-open.c:94
94 = ns->_ns_main_searchlist->r_nlist + to_add + 8;
(and `where` prints the attached stacktrace).
The stacktrace suggests that the ldaudit.so constructor enters the call to
dlopen("liblttng-ust-tracepoint.so.0",...), which eventually triggers a call to
add_to_global() in dl-open.c (in ld.so), where the crash happens.
Initialization of the liblttng-ust-tracepoint.so.0 library (i.e. the execution
of any constructor functions) hasn't even started yet, meaning this is a
genuine ld.so bug. (However, the crash is specific to this particular library.
I wasn't able to reproduce it when dlopen'ing a different library.)
Let me know if there is any other info I should supply.
--
You are receiving this mail because:
You are on the CC list for the bug.