From: Mario Smarduch <cms063@email.mot.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] gdb problem unwinding abort in signal
Date: Fri, 11 Apr 2003 18:17:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705468@msgid-missing> (raw)
When our application aborts in the signal handler (no altstack
is setup) the stack backtrace discontinues at the signal
handler.
(gdb) where
#0 0x20000000000a6342 in kill () at soinit.c:56
#1 0x20000000000a61f0 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x20000000000a8a70 in abort () at ../sysdeps/generic/abort.c:88
#3 0x4000000000000910 in sig_report_and_die ()
Manually unwinding the stack shows the rp set
to ia64_sigtramp(). The privilaged
gate page simplifies allot of things, but it poses a problem
to our software because we send events for
all signals of importance, and count on the core dump
to capture the full call trace prior to and including the
signal - gdb displays this full backtrace on all other
architectures we run on.
If this is the problem how does one get around it
besides manually unwinding the stack?
- mario.
next reply other threads:[~2003-04-11 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 18:17 Mario Smarduch [this message]
2003-04-11 18:29 ` [Linux-ia64] gdb problem unwinding abort in signal David Mosberger
2003-04-11 18:48 ` Mario Smarduch
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=marc-linux-ia64-105590723705468@msgid-missing \
--to=cms063@email.mot.com \
--cc=linux-ia64@vger.kernel.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