From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15760 invoked by alias); 28 Oct 2012 00:02:33 -0000 Received: (qmail 15567 invoked by uid 48); 28 Oct 2012 00:01:21 -0000 From: "bugdal at aerifal dot cx" To: glibc-bugs@sources.redhat.com Subject: [Bug libc/11610] _init/_fini do not have proper unwinding information Date: Sun, 28 Oct 2012 00:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bugdal at aerifal dot cx X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: ppluzhnikov at google dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2012-10/txt/msg00250.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=11610 Rich Felker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugdal at aerifal dot cx --- Comment #4 from Rich Felker 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.