> [EMAIL PROTECTED]:~/src/xcpu/xcpu> acid -l thread 8894
> corpid 8894: text /home/rminnich/src/xcpu/xcpu/o.xcpusrv
> /lib/i686/libm.so.6: linux 386 shared object
> /lib/libutil.so.1: linux 386 shared object
> /lib/i686/libc.so.6: linux 386 shared object
> /lib/ld-linux.so.2: linux 386 shared object
> /usr/local/plan9/acid/port
> /usr/local/plan9/acid/thread
> /usr/local/plan9/acid/386
> acid; threads()
> p=(Proc)0x8066050   // pthread 0x000022be pid 8894  Sched
>
> p=(Proc)0x8066468   // pthread 0x000022c2 pid 8898  Sched
>          t=(_Thread)0x8066728  // Sleeping
> /home/rminnich/src/xcpu/xcpu/xcpusrv.c:1177 chanalt [fsthread]
>
> p=(Proc)0x8078bc0   // pthread 0x000022c8 pid 8904  Running
>          t=(_Thread)0x8078e80  // Running
> /usr/local/plan9/src/lib9p/srv.c:62 read9pmsg
> acid;

It's weird that 8894 has no threads.

> I'm seeing a bit more entries in /proc than I see in the threads()
> display in acid. What am I missing here?

Those three are the only ones you listed in your ps output.
What do you see in /proc?  One could also attach with gdb
and run "thread apply all where" to get an alternate view of
the current thread in each proc.  Useful for sanity checking,
but little else.  stacks() in acid will give you the stack of
every thread, current or not.

Russ

Reply via email to