Anna,
I forgot to mention that once this bbgen test kicks into gear, it never
reports anything. On the main view it is green, but on details of the page
it is purple - and stays that way.
Henrik,
In case it is relevant the core was put in /home/shire/data/acks - not the
usual ~hobbit/server/tmp
It is reproducable - I can kill the ps and restart hobbit, every single
time I start hobbit a few seconds later the CPU is overrun with this one
PID.
Here is the gdb output:
# gdb bin/bbgen ../data/acks/core.31412
GNU gdb Red Hat Linux (6.5-25.el5rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/libpcre.so.0...done.
Loaded symbols for /lib/libpcre.so.0
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Core was generated by `bbgen --recentgifs --subpagecolumns=2 --report'.
Program terminated with signal 6, Aborted.
#0 0x0805274f in calc_pagecolors (phead=0x81ddaa0) at process.c:96
96 for (h = toppage->hosts; (h); h = h->next) {
(gdb) bt
#0 0x0805274f in calc_pagecolors (phead=0x81ddaa0) at process.c:96
#1 0x08049d31 in main (argc=4, argv=0xbfbdd4b4) at bbgen.c:594
Is this what you need?
On 2/1/08, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:
On Fri, Feb 01, 2008 at 12:13:36AM -0500, Josh Luthman wrote:
I have a problem after using the all-in-one patch. ( Last updated:
2007-02-09 10:30 UTC ). The bbgen ps takes the entire CPU and
seemingly
never stops. I've watched it take all the free CPU time for a good
fifteen
minutes now.
bbgen shouldn't take more than a few seconds to run. It's cpu-intensive,
but not that much. So something's broken.
If you haven't done it yet, kill it with a "kill -6 <process-ID>". This
should generate a core file, and it would be interesting to see what the
backtrace is (see the "Reporting bugs" on-line help).
make install as hobbituser and root respectively. Once Hobbit is
started
again, the bbgen ps takes over the CPU.
Sounds like it is reproducible. That's good (for debugging, at least!)
Regards,
Henrik
--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
Those who don't understand UNIX are condemned to reinvent it, poorly.
--- Henry Spencer