From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1500 invoked by alias); 23 Feb 2006 00:41:33 -0000 Received: (qmail 1471 invoked by uid 48); 23 Feb 2006 00:41:30 -0000 Date: Thu, 23 Feb 2006 00:41:00 -0000 Message-ID: <20060223004130.1470.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug other/26208] Serious problem with unwinding through signal frames In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "amodra at bigpond dot net dot au" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-02/txt/msg02604.txt.bz2 List-Id: ------- Comment #20 from amodra at bigpond dot net dot au 2006-02-23 00:41 ------- Created an attachment (id=10895) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10895&action=view) updated for powerpc and powerpc64 Jakub of course is correct that the vdso eh_frame dwarf2 can't increment the pc. I realized that a few minutes after making comment #16, but figured I'd already made enough useless comments on this bug so didn't bother correcting myself. I rather like Jakub's solution. fs->signal_frame would allow us to easily adjust pc in signal frames if necessary, using MD_FROB_UPDATE_CONTEXT. I suppose we could even use MD_FROB_UPDATE_CONTEXT to *set* fs->signal_frame for ppc kernels with vdso. -- amodra at bigpond dot net dot au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #10815|0 |1 is obsolete| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26208