signalling remote threads

Martin Blapp mb at
Sat Mar 10 00:50:20 UTC 2007


>> But is it true for FreeBSD that 'ps -Hauxwww' should show all threads
>> for a process with libc_r,, or ?
> Similarly for libpthread, it will show SOME threads but not as many as there 
> are threads in the process because only threads that are blocked
> for IO in the kernel or are actually running at that instant will
> show up. Threads that are not running or blocked in the kernel
> are, once again just figments of the imagination of the process.
> If you run a libpthread process with LIBPTHREAD_SCOPE_SYSTEM set to 'yes'.
> then it will switch to 1:1 mode and there will be a kernel thread 
> instantiated for each thread in the process and yes you will see them in ps

Ok, this explains why clamd with libpthreads with ps shows only some
of the threads, and I suspected there was something like this. So I definitly
need gdb to attach to a thread to look where it is blocked or what it is
dooing ?

The problem with gdb is that some of the threads are just doing one or
two scans and then they disappear for ever.


More information about the freebsd-threads mailing list