Date: Tue, 16 Sep 2008 18:45:17 +0200 From: "Ivan Voras" <ivoras@freebsd.org> To: "Alfred Perlstein" <alfred@freebsd.org> Cc: stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Apache-worker stuck at 100% CPU Message-ID: <9bbcef730809160945y8f472bfw60af0d22149d9376@mail.gmail.com> In-Reply-To: <20080916164203.GL36572@elvis.mu.org> References: <gadgrb$4uc$1@ger.gmane.org> <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> <20080912225251.GG16977@elvis.mu.org> <9bbcef730809151604i28533745m286e7314810d0362@mail.gmail.com> <20080916022738.GJ36572@elvis.mu.org> <9bbcef730809160212m72fffc7k93d0c92ace2b7c19@mail.gmail.com> <20080916164203.GL36572@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/9/16 Alfred Perlstein <alfred@freebsd.org>: > * Ivan Voras <ivoras@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730809160945y8f472bfw60af0d22149d9376>