Apache-worker stuck at 100% CPU
ivoras at freebsd.org
Tue Sep 16 09:12:02 UTC 2008
2008/9/16 Alfred Perlstein <alfred at freebsd.org>:
> * Ivan Voras <ivoras at freebsd.org> [080915 16:05] wrote:
>> >> How do I pick what thread to backtrace in gdb?
>> > i think the command is 'info threads' or 'show
>> > threads' then i think you just type
>> > 'thread FOO' to select the thread.
>> Both commands don't work / don't exist. Any others?
>> (background: apache22-worker port, no mod_php, on 7.0 and 7-STABLE
>> suddenly gets stuck at 100% CPU; the same setup worked on 6-STABLE.
>> I'm looking for ideas)
> I'm sorry, I really can't help at this point other than to look
> through the documents myself to figure out how to do a backtrace/select
> Give it a shot, and let us know and we can go further.
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.
More information about the freebsd-threads