GDB & info threads command

GDB & info threads command

[Jeff Jenkins]

Hi,

I have GDB sources from 03/06/02 running on RH7.2 (kernel 2.4.7-10).
I created a multi-threaded app that created 100 threads, and then promptly
dumps core.
(on purpose!)

I fire up "gdb test core" and do an "info threads" and all I get is one
thread, namely the thread
that caused the SIGSEGV.  I was expecting to see the stacks from all 100
threads.  Is there a fix for this?  Do I need a newer kernel?

Any help would be groovey!

Thanks!

-- jrj

Re: GDB & info threads command

[Daniel Jacobowitz]

On Thu, Mar 07, 2002 at 07:22:07PM -0800, Jeff Jenkins wrote:
> 
> Hi,
> 
> I have GDB sources from 03/06/02 running on RH7.2 (kernel 2.4.7-10).
> I created a multi-threaded app that created 100 threads, and then promptly
> dumps core.
> (on purpose!)
> 
> I fire up "gdb test core" and do an "info threads" and all I get is one
> thread, namely the thread
> that caused the SIGSEGV.  I was expecting to see the stacks from all 100
> threads.  Is there a fix for this?  Do I need a newer kernel?
> 
> Any help would be groovey!

No Linux kernel currently dumps the thread registers to coredumps. 
Hopefully I'll get a chance to submit the patches for that in a month
or two.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Re: GDB & info threads command

[Daniel Jacobowitz]

On Thu, Mar 07, 2002 at 08:17:00PM -0800, Jeff Jenkins wrote:
> So, just to be thorough, this is a limitation of the kernel, not GDB. Right?

Right.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Re: GDB & info threads command

[Andrew Cagney]

Sounds like something to file a dummy bug report against.

> On Thu, Mar 07, 2002 at 08:17:00PM -0800, Jeff Jenkins wrote:
> 
>> So, just to be thorough, this is a limitation of the kernel, not GDB. Right?
> 
> 
> Right.



Andrew

RE: GDB & info threads command

[Jeff Jenkins]

Yea.  I can't imagine how BIG apps (meaning lots of threads) would survive
without this *feature*.  Being able to load the core file and examine all
the threads at the time of the core is invaluable!  Do this all the time
with dbx on Solaris.  I guess I am spoiled...

-- jrj

-----Original Message-----
From: Andrew Cagney [mailto:ac131313@cygnus.com]
Sent: Thursday, March 07, 2002 9:19 PM
To: Daniel Jacobowitz
Cc: Jeff Jenkins; gdb@sources.redhat.com
Subject: Re: GDB & info threads command


Sounds like something to file a dummy bug report against.

> On Thu, Mar 07, 2002 at 08:17:00PM -0800, Jeff Jenkins wrote:
>
>> So, just to be thorough, this is a limitation of the kernel, not GDB.
Right?
>
>
> Right.



Andrew