This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/11610] _init/_fini do not have proper unwinding information
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Sun, 28 Oct 2012 00:01:20 +0000
- Subject: [Bug libc/11610] _init/_fini do not have proper unwinding information
- Auto-submitted: auto-generated
- References: <bug-11610-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11610
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #4 from Rich Felker <bugdal at aerifal dot cx> 2012-10-28 00:01:20 UTC ---
I'm curious what the "right" behavior in this circumstance would be. Are you
suggesting dlopen should catch the exception and back out the whole operation?
I question whether that's possible/safe at the point where ctors are already
being called. If dlopen did not catch it but just let the caller catch it, what
would the caller be expected to do? Throwing exceptions from global ctors
(well, even having global ctors to begin with, but that's another topic
entirely) just strikes me as a flawed library design.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.