RE: User level threads debugging with GDB

["Paul Koning" <Paul_Koning at Dell dot com>]

I've just gone through this for NetBSD...

If your platform has a libthread_db then it seems sensible to use that
and interface GDB to it, as Linux does (or can do; it doesn't seem to do
it in all cases).  If not, then you don't need to create one.  Some
existing files offer various pieces of the answer that you can use.  For
example, dec-threads.c is short and simple but not necessarily a
complete answer.  linux-nat.c is very helpful but a bunch of what it
does exists because of extra work needed on Linux.

Stack printing relies on the register access routines; those have to
work per thread.  If they do then the rest just works.

I found the main changes were in the "wait" and "resume" routines.  In
"wait" because after the wait finishes you want to get the list of
threads and their status, and use the GDB routines that update GDB's
list of threads.  In  "resume" because you need to be able to step and
continue a single thread as well as all threads.  

For any given platform, I expect that you'll find parts of the answer in
several of the existing threads support files, but probably not the
whole answer in any one of them.

	paul

> -----Original Message-----
> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
> Behalf Of PILLON Julien
> Sent: Friday, April 09, 2010 4:13 AM
> To: gdb@sourceware.org
> Subject: User level threads debugging with GDB
> 
> Hi,
> I would like to know the right way to do some user-level threads
> debugging with GDB and I have a few questions :
> First, the main work will be within the libthread_db (especially in
the
> td_ta_new function I guess) but what else must be modified and what
can
> be left as is ?
> Next, how should I implement the stack printing ?
> Is the attach mode altered with this kind of modifications ? And if it
> is, where are the sources to modify ?
> 
> regards
> 
> Julien