All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Backtrace problems from a signal handler
Date: Wed, 27 Jul 2005 01:09:58 +0000	[thread overview]
Message-ID: <4459.1122426598@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <13701.1122269352@kao2.melbourne.sgi.com>

On Mon, 25 Jul 2005 15:29:12 +1000, 
Keith Owens <kaos@sgi.com> wrote:
>gdb with libunwind support does not unwind correctly if a signal
>handler calls another function which then takes a core dump.
>
>SuSE SLES9 SP2.  gdb-6.3-16.4.  libunwind-0.98.5-3.2.  gcc 3.3.3.

David Mosberger suggested checking the CVS version of gdb.  The
gdb-6.3.50.20050726 snapshot handles backtrace through a signal
handler when the handler calls another function.

Program received signal SIGABRT, Aborted.
0xa000000000010641 in __kernel_syscall_via_break ()
(gdb) bt
#0  0xa000000000010641 in __kernel_syscall_via_break ()
#1  0x20000000000a8690 in raise () from /lib/tls/libc.so.6.1
#2  0x20000000000aadf0 in abort () from /lib/tls/libc.so.6.1
#3  0x4000000000000740 in foo () at signal-test.c:6
#4  0x4000000000000780 in handler (sig\x14) at signal-test.c:12
#5  <signal handler called>
#6  0xa000000000010640 in __kernel_syscall_via_break ()
#7  0x20000000000a8a80 in kill () from /lib/tls/libc.so.6.1
#8  0x4000000000000810 in main () at signal-test.c:18


      reply	other threads:[~2005-07-27  1:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25  5:29 Backtrace problems from a signal handler Keith Owens
2005-07-27  1:09 ` Keith Owens [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=4459.1122426598@kao2.melbourne.sgi.com \
    --to=kaos@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.