From: "Paul Pluzhnikov" <ppluzhnikov@google.com>
To: "ying lcs" <yinglcs@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: how can I dump out thread informations in gdb
Date: Wed, 22 Oct 2008 20:05:00 -0000 [thread overview]
Message-ID: <8ac60eac0810221304n4c244406ja26b0be0e6653d5b@mail.gmail.com> (raw)
In-Reply-To: <568e62a40810221301t301c7d46o9e1d4446d54abc7f@mail.gmail.com>
On Wed, Oct 22, 2008 at 1:01 PM, ying lcs <yinglcs@gmail.com> wrote:
> Can you please tell me how can I print out what are all the existing
> threads in my programs (while I hit a breakpoint)?
> And what are the stack trace of each of those threads?
RTFM?
info threads
thread apply all where
--
Paul Pluzhnikov
next prev parent reply other threads:[~2008-10-22 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 20:02 ying lcs
2008-10-22 20:05 ` Paul Pluzhnikov [this message]
2008-10-22 20:14 ` Bradshaw, James
2008-10-23 2:30 ` Paul Pluzhnikov
2008-10-22 20:06 ` Joel Brobecker
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=8ac60eac0810221304n4c244406ja26b0be0e6653d5b@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=yinglcs@gmail.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