On Thu, Nov 27, 2003 at 06:25:38PM -0600, Dan Nelson wrote: > In the last episode (Nov 27), Chris Elsworth said: > > Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9 > > system. However, today, unexplicably, it's run into the same problem > > 3 times now; a couple of the threads suddenly start eating 100% CPU > > for no good reason while doing a SELECT. They'll sit there until I > > kill them, which results in a lot of hair tearing as it comes back up > > checking all the tables. > > > > I haven't been able to produce a core despite sending it a SIGABRT, > > but I'll try recompiling with -g (do the supplied binaries have this?) > > soon. > > You can use the gcore command to create a coredump of a running program > without killing it, and the pstack command (in ports) is handy for > printing the stacks of all threads in a running process without even > coring it. Once you get a stack trace, send it to > [EMAIL PROTECTED] and/or here.
Please do post a strack trace here. I'd very curious to see what it looks like. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 75 days, processed 2,959,075,536 queries (456/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
