From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18799 invoked by alias); 29 Jun 2009 09:43:41 -0000 Received: (qmail 18784 invoked by uid 48); 29 Jun 2009 09:43:41 -0000 Date: Mon, 29 Jun 2009 09:43:00 -0000 Message-ID: <20090629094341.18783.qmail@sourceware.org> From: "informkarthik at gmail dot com" To: gdb-prs@sourceware.org In-Reply-To: <20090622172820.10310.informkarthik@gmail.com> References: <20090622172820.10310.informkarthik@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug backtrace/10310] (GNU/Linux:GCC:C lang: ARM platform) Core dump backtrace on stripped binaries Halts in 2 levels X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2009-q2/txt/msg00196.txt.bz2 ------- Additional Comments From informkarthik at gmail dot com 2009-06-29 09:43 ------- We figured out that this is specific to our target. There were two things that we had to do. 1) Enable apcs-frame option for gcc. 2) Change the program counter correction to 12 (instead of 8). This is machine specific. --- gdb/arm-tdep.c.orig 2009-06-29 15:14:52.000000000 +0530 +++ gdb/arm-tdep.c 2009-06-29 14:46:41.000000000 +0530 @@ -1366,7 +1366,7 @@ else { prologue_start = gdbarch_addr_bits_remove - (gdbarch, return_value) - 8; + (gdbarch, return_value) - 12; prologue_end = prologue_start + 64; /* See above. */ } } 3) I think we need a comment in arm_scan_prologue, that one needs correction of 12 in some architectures for stack unwinding to work. Do we have any compiler flags that we can use to incorporate this as a feature that the user can set while compiling? -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING http://sourceware.org/bugzilla/show_bug.cgi?id=10310 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.