This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Debug threads

From: Michael Snyder <msnyder at vmware dot com>
To: hce <webmail dot hce at gmail dot com>
Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Fri, 13 Aug 2010 17:01:30 -0700
Subject: Re: Debug threads
References: <AANLkTin2aM7+C3qd8LoULhoY7Pm3GsN=sWLobv368nWO@mail.gmail.com>

hce wrote:

Hi,

I am debug a problem on CentOS 5, the problem used %100 CPU and there
are 9 threads running. Which gdb command can I find out which thread
is current running and  hooked %100 CPU?


If you can attach with gdb, then there is a high probability that
the "current" thread is the one that is eating up all the CPU.

Do "info threads", and look for the thread that has an asterisk
("*") in the left hand column.

If you do "continue" and then control-c and repeat the info threads
command, it is likely that the busy thread will remain as the
"current" thread each time (or the majority of times).

Otherwise, gdb does not have a formal way of showing you which
thread is the most busy.

Michael

Follow-Ups:
- Re: Debug threads
  - From: Paul Koning

References:
- Debug threads
  - From: hce

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]