According to Rivera, Tony:
> I will check and delete any .db files and rerun the "rundig" script.
> If I can get a "gdb" debugger, how do you use it to get the information you
> are looking for. I have never used gdb before, I am interested in learn how
> though.
I see from your later message that you figured it out. I've never learned
much about gdb, so I'm not the expert here. I know "run" and "bt", and most
other debugging I do with trace prints.
> Did any of the output from the "rundig -vvv" mean anything more to you?
Not really. It looked pretty normal to me, but it seemed to end abruptly.
I guess I usually use -s with -vvv, so I'm used to seeing the stats at the
end of the run. It might be worth a try running "htdig -ivvvvs" separately,
which will generate tons of output, and looking at what happens just before
it ends, to really confirm whether it is htdig itself that's dying, and what
it's doing when it dies.
and later on...
> I have loaded gdb rev 5.0 on my system, deleted all db. files that were
> copied from the sun system and rerun the rundig script with -vvv options. I
Not just the db.* files, but also the synonyms.db file in the common
directory must be deleted.
> am attaching the output from
>
> gdb /opt/www/htdig/bin/htdig ./core
> bt
> quit
That's the right sequence of commands, but there was no attachement to
your e-mail.
--
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
