Here is the output after loading htdig into gdb and running it:
Program received signal SIGSEGV, Segmentation Fault
0x4002e1d1 in ifstream::~ifstream()
Current language: auto, currently c
Here is the backtrace info:
#0 0x4002e1d1 in ifstream::~ifstream()
#1 0x8059eff in Configuration::Read (this=0x80a7510,
filename=0x80aa078 "/home/bkcobb/htdig/conf/htdig.conf")
at Configuration.cc:350
#2 0x8053779 in main (ac=1, av=0xbffffdb4) at htdig.cc:104
I am logged on at the console as root when I run the gdb session in the
/home/bkcobb/htdig/bin directory.
I've tried using the htdig.conf "out of the box" as well as the one I had
customized
when I had a working installation.
I upgraded the Linux kernel to 2.2.6 from 2.0.34 since my last successful
htdig upgrade if that helps. Someone had mentioned library or other source
file dependencies. Is there a FAQ on this somewhere?
> -----Original Message-----
> From: Geoff Hutchison [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 02, 1999 8:47 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [htdig] RE: HTDIG seg faults and dumps core on RH Linux
> Kernel
>
>
> On Fri, 2 Jul 1999, Cobb, Brian wrote:
>
> > Just for grins I re-downloaded ver 3.1.1. I get the same behavior now
> with
> > it after a sucessful compile. Anybody else experienced something
> similar?
>
> This sounds like some includes or libraries changed. You should also take
> a look at what compiler you're using.
>
> Finally, with a segfault, it's greatly appreciated to get some
> information from the core file. If you have gdb, it would be great to get
> some information from the core like a stack backtrace.
>
> -Geoff Hutchison
> Williams Students Online
> http://wso.williams.edu/
>
> ------------------------------------
> To unsubscribe from the htdig mailing list, send a message to
> [EMAIL PROTECTED] containing the single word "unsubscribe" in
> the SUBJECT of the message.
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
