From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb@sources.redhat.com
Subject: backtrace from signal handler
Date: Tue, 11 May 2004 18:08:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0405111249560.20088@lazy> (raw)
I understand that a new backtrace mechanism was implimented (by andrew
cagney) in the mainline CVS version of GDB, are there any patche (or
patches) available for this? I would like to use them to backport to GDB
6.1. It fixes backtracing from signal handler. It also will solve a ton of
problmes wrt backtracing using GDB 6.1 on powerpc 64, coz mainline GDB
works well for debugging powerpc, but we are still using 6.1 level.
Thanks a ton
------------
Manoj Iyer
next reply other threads:[~2004-05-11 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 18:08 Manoj Iyer [this message]
2004-05-13 22:21 ` Andrew Cagney
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=Pine.LNX.4.58.0405111249560.20088@lazy \
--to=manjo@austin.ibm.com \
--cc=gdb@sources.redhat.com \
/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