[137] in Pthreads mailing list archive

home help back first fref pref prev next nref lref last post

Re: pthread.h : pthread_wait_data

daemon@ATHENA.MIT.EDU (sudhir halbhavi)
Mon Oct 9 12:37:04 1995

Date: Mon, 9 Oct 1995 11:00:17 -0500 (CDT)
From: sudhir halbhavi <halbhavi@eecs.ukans.edu>
To: "William S. Gribble" <grib@cs.utexas.edu>
Cc: pthreads@MIT.EDU
In-Reply-To: <199510091517.KAA04069@cascade.cs.utexas.edu>


On Mon, 9 Oct 1995, William S. Gribble wrote:

> From: sudhir halbhavi <halbhavi@eecs.ukans.edu>
> > (gdb) ls-t
> > Number of threads = 6
> > Thread_pointer = 0x16978 (92536), Thread_id = 1
.....
> > 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!

 This is from a debugger we are building here (I had sent a brief mail 
about it before). It is still evolving. It has a tcl extension, which 
allows the user to write scripts which gets executed when a specific 
breakpoint is hit. This has proved to be a very powerful feature for data 
enumeration, thread specific breakpoints and also with a little ingenuity 
can be used to debug concurrency anamolies like data races, etc.

 There is still work to be done. We will make the source public domain soon.

Sudhir


home help back first fref pref prev next nref lref last post