This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/17702] Support recursive dlopen.
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 15 Dec 2014 14:47:19 +0000
- Subject: [Bug dynamic-link/17702] Support recursive dlopen.
- Auto-submitted: auto-generated
- References: <bug-17702-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17702
--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to johnandsara2 from comment #1)
> dlopen should only connect to a lib, not cause any "initializations"
It does run code and it should.
After the library is loaded and relocations resolved it runs initializer
functions, constructors, and static data initializers, all of which are
required to correctly access the data and or functions in the library.
Similarly it may run finialization functions and destructors at unload time.
Is there any particular standard interpretation or use case that you think
needs a "connect but don't yet use" semantic?
--
You are receiving this mail because:
You are on the CC list for the bug.