Apache-worker stuck at 100% CPU

Ivan Voras ivoras at freebsd.org
Tue Sep 16 16:45:18 UTC 2008


2008/9/16 Alfred Perlstein <alfred at freebsd.org>:
> * Ivan Voras <ivoras at freebsd.org> [080916 02:12] wrote:

>> Sorry, I should have been more verbose - "info threads" should work
>> but it doesn't - I can attach and get threads from a "regular"
>> multithreaded process, but when yesterday when I attached to the stuck
>> process, I couldn't get the list of threads. I'll try again the next
>> time it gets stuck and try to provide more information.
>
> If it happens again, you could try sending it a SIGABRT or SEGV
> and then trying to diagnose the core dump.
>
> Or try using gcore to generate a coredump and debug that.

It happens approximately every two days; I've rebuild apache with
debugging symbols so it will be easier to dig around this time.


More information about the freebsd-threads mailing list