public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "informkarthik at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/10310] (GNU/Linux:GCC:C lang: ARM platform) Core dump backtrace on stripped binaries Halts in 2 levels
Date: Tue, 23 Jun 2009 07:03:00 -0000 [thread overview]
Message-ID: <20090623070307.8154.qmail@sourceware.org> (raw)
In-Reply-To: <20090622172820.10310.informkarthik@gmail.com>
------- Additional Comments From informkarthik at gmail dot com 2009-06-23 07:03 -------
(In reply to comment #0)
> 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.
I see it even in unstripped binaries right now.. it looks like this
(gdb) bt
#0 0x00008344 in temp3 ()
#1 0x00008358 in temp2 ()
#2 0x00008358 in temp2 ()
#3 0x00008370 in temp1 ()
#4 0x000083a0 in main ()
Look at temp2. Note all the funtions just call the next function and do nothing
else. temp3 has while(1) in it so that i can send a signal and get core dump.
The stack looks like the following:
(gdb) x/16w $sp-12
0x56d7dd34: 0x00008294 0x00000000 0x00000000 0x56d7dd4c
0x56d7dd44: 0x00008358 0x56d7dd54 0x00008370 0x56d7dd64
0x56d7dd54: 0x000083a0 0x00000005 0x40024e00 0x00000000
0x56d7dd64: 0x4003aff4 0x40153000 0x56d7deb4 0x00000001
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
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.
next prev parent reply other threads:[~2009-06-23 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 17:28 [Bug backtrace/10310] New: " informkarthik at gmail dot com
2009-06-23 7:03 ` informkarthik at gmail dot com [this message]
2009-06-29 9:43 ` [Bug backtrace/10310] " informkarthik at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090623070307.8154.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).