Date: Tue, 16 Sep 2008 11:12:01 +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: <9bbcef730809160212m72fffc7k93d0c92ace2b7c19@mail.gmail.com> In-Reply-To: <20080916022738.GJ36572@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>
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> [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 > threads. > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730809160212m72fffc7k93d0c92ace2b7c19>