This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dynamic-link/16592] crash in startup


https://sourceware.org/bugzilla/show_bug.cgi?id=16592

--- Comment #8 from Stefan Seefeld <stefan at codesourcery dot com> ---
I have managed to isolate the problem to a library constructor (function marked
as __attribute__((constructor)) ) causing the crash.

What I don't understand is why this constructor fails in this situation (of
being part of an audit library), when it doesn't fail during normal linking &
loading.

Shouldn't the loader take care of initializing the libraries in proper order
(as determined by symbol dependency analysis) ? Or is there in fact no
guarantee of order of initialization, and the library was just lucky enough to
always be initialized "late enough" until I started using it as part of an
auditor ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


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