From: Ivan Novick <inovick@fastmail.co.uk>
To: gdb@sourceware.org
Subject: btacktrace on all threads
Date: Sat, 21 Jan 2006 18:50:00 -0000 [thread overview]
Message-ID: <43D28228.10105@fastmail.co.uk> (raw)
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.
Thanks for any tips or tricks on this subject you have figured out or
can think of.
Ivan
next reply other threads:[~2006-01-21 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 18:50 Ivan Novick [this message]
2006-01-21 20:36 ` Daniel Jacobowitz
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=43D28228.10105@fastmail.co.uk \
--to=inovick@fastmail.co.uk \
--cc=gdb@sourceware.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