From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-11254-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 21211 invoked by alias); 19 May 2010 14:45:04 -0000
Received: (qmail 21032 invoked by uid 48); 19 May 2010 14:44:48 -0000
Date: Wed, 19 May 2010 14:45:00 -0000
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Message-ID: <20100519144447.11610.pasky@suse.cz>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug libc/11610] New: _fini does not have proper unwinding information on x86_64
X-Bugzilla-Reason: CC
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
X-SW-Source: 2010-05/txt/msg00076.txt.bz2

It is impossible to reliably unwind the stack above _fini() on x86_64 since no
unwind information is provided for it and it modifies a stack register. This
matters for gdb backtracing - if a process crashes within a destructor, it can
frequently be essential to look at why the program began terminating in the
first place.

-- 
           Summary: _fini does not have proper unwinding information on
                    x86_64
           Product: glibc
           Version: 2.12
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: pasky at suse dot cz
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=11610

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.