According to Rivera, Tony:
> Gilles,
> Thank you for responding to my email. I have rerun the ./rundig command and
> tee'd off the output. The following is a copy of the output from the rundig
> script. I am looking for the debugger gdb that you mentioned. No luck. I am
> attaching a compressed copy of the core file that was in /opt/www/htdig/bin
I can't do anything with a core file from another system. The core file
must be matched up with the executable file that generated it, in order to
make sense of it, and it must be analysed with a debugger for that same system.
If you have no debugger, gdb or other, then you're out of luck in analysing
the dump. However, I have a hunch...
> DB2 problem...: unrecognized file type
> ./rundig[37]: 4394 Bus error(coredump)
This error only happens after htdig and htmerge run for some time and
produce output. I'm wondering if it's not htfuzzy that's producing the
core dump. Did you happen to copy over any .db files from your Sun system
to the HP system? If so, you should delete them, as their formats are
incompatible.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
