[135] in Pthreads mailing list archive
Re: pthread.h : pthread_wait_data
daemon@ATHENA.MIT.EDU (William S. Gribble)
Mon Oct 9 12:01:37 1995
From: "William S. Gribble" <grib@cs.utexas.edu>
Date: Mon, 9 Oct 1995 10:17:08 -0500
To: halbhavi@eecs.ukans.edu
Cc: pthreads@MIT.EDU
In-Reply-To: <Pine.3.87.9510081618.A14414-0100000@mitchell> (message from sudhir halbhavi on Sun, 8 Oct 1995 16:53:19 -0500 (CDT))
From: sudhir halbhavi <halbhavi@eecs.ukans.edu>
> (gdb) ls-t
> Number of threads = 6
> Thread_pointer = 0x16978 (92536), Thread_id = 1
> Thread_pointer = 0x16d78 (93560), Thread_id = 2
> Thread_pointer = 0x16f78 (94072), Thread_id = 3
> Thread_pointer = 0x17178 (94584), Thread_id = 4
> Thread_pointer = 0x17378 (95096), Thread_id = 5
> Thread_pointer = 0x17578 (95608), Thread_id = 6 ****
OK -- how did you generate this output from gdb? This is *not*
a standard feature of any gdb I know about, and it would make it
much easier to debug pthreads codes!
With this kind of output ability, you're just about a half a step from
being able to generate a menu of running threads to switch to under
Emacs GUD. This is the one thing that my friends who use Code Warrior
on the Mac can still taunt me about. Any info appreciated.
Thanks,
Bill Gribble
