This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/10310] (GNU/Linux:GCC:C lang: ARM platform) Core dump backtrace on stripped binaries Halts in 2 levels
- From: "informkarthik at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 29 Jun 2009 09:43:41 -0000
- Subject: [Bug backtrace/10310] (GNU/Linux:GCC:C lang: ARM platform) Core dump backtrace on stripped binaries Halts in 2 levels
- References: <20090622172820.10310.informkarthik@gmail.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- 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.