This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: how can I dump out thread informations in gdb
- From: "Bradshaw, James" <jbradsha at enterasys dot com>
- To: Paul Pluzhnikov <ppluzhnikov at google dot com>, ying lcs <yinglcs at gmail dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Wed, 22 Oct 2008 16:13:16 -0400
- Subject: RE: how can I dump out thread informations in gdb
- Accept-language: en-US
- Acceptlanguage: en-US
- References: <568e62a40810221301t301c7d46o9e1d4446d54abc7f@mail.gmail.com><8a c60eac0810221304n4c244406ja26b0be0e6653d5b@mail.gmail.com>
And when "info threads" gives the incorrect information, how exactly do we address that problem? I gather from earlier posts, libthread_db on the target must not be stripped in order to correctly view threads--at least on linux targets that have nptl support. Is that the only requirement?
-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf Of Paul Pluzhnikov
Sent: Wednesday, October 22, 2008 4:04 PM
To: ying lcs
Cc: gdb@sourceware.org
Subject: Re: how can I dump out thread informations in gdb
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