On Wed, Mar 08, 2006 at 04:05:43AM -0800, Tom Andersen wrote: > We're running Dbmail 2.0.4 on Debian Linux > 2.6.12-1-686-smp with MySQL 4.0.26 on Dell 1850 with 2 > * Xeon 3.20 and 3GB RAM. > > We spent some time patching Dbmail to fit with our > database etc, and we've spent a long time trying to > troubleshoot the CPU bug. > > We've compiled Dbmail with CFLAGS="-Wall -O3 -g" as > recommended here. > > Here is some debug output. Any insights you're able to > provide would be greatly appreciated.
Thinking about this some more, here are additional random thoughts you might want to try attaching GDB several times (continue and then ^C the process to return to GDB) and see if it's in the same area of code. You could also try compiling with CFLAGS="-fno-omit-frame-pinter -pg" LDFLAGS="-pg" and looking at the profile output. Unfortunately, I've had bad luck with actually being able to nab a specific profile from the filesystem because of the fork()ing of the daemon--newer versions of gcc supposedly allow for PID addition to the filename... You could then check to see if there is a particular place where the code is hanging. Also try attaching a strace -p or ltrace -p to the spinning daemon and seeing if it happens to be calling certain system/library functions repeatedly. No real ideas, but maybe something will shed more light. Matt
