From: Daniel Jacobowitz <drow@false.org>
To: Ivan Novick <inovick@fastmail.co.uk>
Cc: gdb@sourceware.org
Subject: Re: btacktrace on all threads
Date: Sat, 21 Jan 2006 20:36:00 -0000 [thread overview]
Message-ID: <20060121185028.GA4861@nevyn.them.org> (raw)
In-Reply-To: <43D28228.10105@fastmail.co.uk>
On Sat, Jan 21, 2006 at 06:49:12PM +0000, Ivan Novick wrote:
> Hi,
>
> Is there an easier way to backtrace all threads in a core file.
>
> What I am doing now is getting the list of thread numbers manually with
> info threads and then going to each thread individually and running
> backtrace there.
"thread apply all backtrace"
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-01-21 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 18:50 Ivan Novick
2006-01-21 20:36 ` Daniel Jacobowitz [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=20060121185028.GA4861@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=inovick@fastmail.co.uk \
/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