From: "Shane Volpe" <shanevolpe@gmail.com>
To: "Harald Schiöberg" <harald@net.t-labs.tu-berlin.de>
Cc: gdb@sourceware.org
Subject: Re: gdb backtrace after SIGILL on Xscale (ARM)
Date: Mon, 29 Sep 2008 20:03:00 -0000 [thread overview]
Message-ID: <8c7950360809291303q37de5e65h7dbf28707a5c8d29@mail.gmail.com> (raw)
In-Reply-To: <48DC9EA0.4040509@net.t-labs.tu-berlin.de>
Harald,
Thanks for the feedback but I'm not sure it is the same issue. In the
thread you referenced
"http://sourceware.org/ml/gdb/2008-01/msg00032.html" it looks like a
SIGILL was happening after a breakpoint and there was valid gdb
backtrace data present. What I'm seeing is there is NO backtrace data
available after a SIGILL, this makes it impossible to use gdb for
debugging the cause of a SIGILL in my application. I think my problem
is more like that of the following thread:
"http://sourceware.org/ml/gdb/2007-03/msg00155.html" In fact that
thread was started by a co-worker of mine, we were never able to get
it working and gave up on it but now I want to get to the bottom of
the issue and get gdb working for backtracing SIGILLs on an ARM EABI
GLIBC system.
Summery of my system:
gdb version: 6.8
glibc version: 2.5
ARCH: PXA270 (xscale)
Linux Version: 2.6.23 (Distro: OpenEmbedded)
Regards,
Shane
prev parent reply other threads:[~2008-09-29 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 17:28 Shane Volpe
2008-09-26 8:35 ` Harald Schiöberg
2008-09-29 20:03 ` Shane Volpe [this message]
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=8c7950360809291303q37de5e65h7dbf28707a5c8d29@mail.gmail.com \
--to=shanevolpe@gmail.com \
--cc=gdb@sourceware.org \
--cc=harald@net.t-labs.tu-berlin.de \
/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