how can I dump out thread informations in gdb

how can I dump out thread informations in gdb

[ying lcs]

Hi,

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?

Thank you.

Re: how can I dump out thread informations in gdb

[Paul Pluzhnikov]

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

RE: how can I dump out thread informations in gdb

[Bradshaw, James]

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

Re: how can I dump out thread informations in gdb

[Paul Pluzhnikov]

On Wed, Oct 22, 2008 at 1:13 PM, Bradshaw, James <jbradsha@enterasys.com> wrote:

> And when "info threads" gives the incorrect information, how exactly
> do we address that problem?

OP gave no indication that he gets incorrect information.

> I gather from earlier posts, libthread_db
> on the target must not be stripped in order to correctly view threads

That is incorrect. AFAICT, libthread_db may be stripped
(it must have dynamic symbol table intact; but strip normally
doesn't touch dynamic symbol table anyway).

However, on Linux libpthread.so.0 itself must not be stripped,
or libthread_db will refuse to work with it.

> at least on linux targets that have nptl support.

Same applies to LinuxThreads.

> Is that the only requirement?

No: libthread_db.so.1 must match libpthread.so.0 (both must
come from the same version of glibc).

-- 
Paul Pluzhnikov

Re: how can I dump out thread informations in gdb

[Joel Brobecker]

> 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?

I really recommend that you take a look at the GDB documentation:
http://sourceware.org/gdb/current/onlinedocs/gdb_toc.html

There is a section about debugging programs with multiple threads:
http://sourceware.org/gdb/current/onlinedocs/gdb_5.html#SEC28

and also a section about how to get a backtrace:
http://sourceware.org/gdb/current/onlinedocs/gdb_8.html#SEC54

-- 
Joel