Hobbitd_history crashing

[Stuffle, David]

Hobbit 4.0.4
Fedora Core 3

My hobbitd_history has crashed several times in the past few weeks.  It goes
red with "Fatal signal caught" then it goes purple.  I have core files in
the server/tmp directory.  Here is the debug output you have requested in a
previous post.  Thanks!

-bash-3.00$ gdb bin/hobbitd_history tmp/core.26954
GNU gdb Red Hat Linux (6.1post-1.20040607.41rh)
Copyright 2004 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/tls/libthread_db.so.1".

Core was generated by `hobbitd_history'.
Program terminated with signal 6, Aborted.
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0  0x003ff7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0  0x003ff7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x0043f955 in raise () from /lib/tls/libc.so.6
#2  0x00441319 in abort () from /lib/tls/libc.so.6
#3  0x0804d5de in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  0x0804a242 in main (argc=1, argv=0xfef4a724) at hobbitd_history.c:194
(gdb) 



~~~~~~~~~~~~~~
David Stuffle                       dstuffle at deltafaucet.com       
Delta Faucet Company                (317) 571-4301


This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.