[Bug backtrace/10310] New: (GNU/Linux:GCC:C lang: ARM platform) Core dump backtrace on stripped binaries Halts in 2 levels

["informkarthik at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

Backtrace on stripped binaries in ARM platform do not go beyond two levels. gdb
throws 'identical frame' (corrupt stack) message. Noticed that gdb takes the
path of stack unwinding using frame pointer and standard stack frame structure.
How reliable is this?

Steps to reproduce: 
1) Just build using the following compiler options 
-mabi=aapcs-linux -mno-thumb-interwork -fno-strict-aliasing -fno-common -Os
-fno-strict-aliasing -fno-common -marm -mhard-float -mfloat-abi=softfp -mfpu=vfp
-mno-sched-prolog  -march=armv5te -mtune=marvell-f -fno-optimize-sibling-calls
-fno-stack-protector -fno-omit-frame-pointer  -fPIC.
2) send sigsegv or sigabrt to the app.
3) core dumped.
4) arm-none-linux-gnueabi-gdb app core
5) bt gives only two levels of addresses and halts with the message
previous frame identical to this frame (corrupt stack?).
---
Noticed similar output in my x86 setup also.. except that it prints the same
couple of addresses twice before exiting with the 'identical frame' message.

-- 
           Summary: (GNU/Linux:GCC:C lang: ARM platform) Core dump backtrace
                    on stripped binaries Halts in 2 levels
           Product: gdb
           Version: 6.8
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: backtrace
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: informkarthik at gmail dot com
                CC: gdb-prs at sourceware dot org


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.