From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6584 invoked by alias); 22 Feb 2006 01:13:58 -0000 Received: (qmail 6512 invoked by uid 48); 22 Feb 2006 01:13:55 -0000 Date: Wed, 22 Feb 2006 01:13:00 -0000 Message-ID: <20060222011355.6511.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/msg02471.txt.bz2 List-Id: ------- Comment #15 from amodra at bigpond dot net dot au 2006-02-22 01:13 ------- ppc vdso caters for pc-1 with the following. /* The nop here is a hack. The dwarf2 unwind routines subtract 1 from the return address to get an address in the middle of the presumed call instruction. Since we don't have a call here, we artifically extend the range covered by the unwind info by padding before the real start. */ nop .balign 8 V_FUNCTION_BEGIN(__kernel_sigtramp_rt64) .Lsigrt_start = . - 4 addi r1, r1, __SIGNAL_FRAMESIZE li r0,__NR_rt_sigreturn sc .Lsigrt_end: -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26208