Hi, Gilles:
The gdb output is listed below:
Starting program: /usr/bin/htdig -i
Program received signal SIGSEGV, Segmentation fault.
0x40147e7d in HtDateTime::SettoNow () at eval.c:41
41 eval.c: No such file or directory.
in eval.c
(gdb) % Total % Received % Xferd Average Speed Time
Curr.
Dload Upload Total Current Left
Speed
100 309 0 309 0 0 2160 0 --:--:-- 0:00:00 --:--:--
0
(gdb) bt
#0 0x40147e7d in HtDateTime::SettoNow () at eval.c:41
#1 0x0805995b in String::operator= () at eval.c:41
#2 0x0804dd40 in String::operator= () at eval.c:41
#3 0x08058797 in String::operator= () at eval.c:41
#4 0x08052b23 in String::operator= () at eval.c:41
#5 0x0805aceb in String::operator= () at eval.c:41
#6 0x402f5627 in __libc_start_main (
main=0x805a100 <String::operator=(char const *)+55688>, argc=2,
ubp_av=0xbffffb04, init=0x804b970 <_init>, fini=0x805d7b0 <_fini>,
rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffffafc)
at ../sysdeps/generic/libc-start.c:129
(gdb)
Please let me know if there is more info you need to debug this htdig
external_protocols issue.
Thank you.
Jin
-----Original Message-----
From: Gilles Detillieux [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 10, 2002 4:22 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [htdig] htdig seg. fault after adding external_protocols
option.
According to Tsai, Jin:
> Hi, Gilles:
>
> Thanks for your prompt response.
>
> 1. I have followed the FAQ 5.14 instruction to recompile
> htdig-3.2.0-1.b4.0.72 src RPM package with the HAVE_BROKEN_REGEX define to
1
> and remove the htlib/regex.h, but the recompiled htdig -i -vvvvvv still
gave
> me seg. fault.
The instructions that you followed in FAQ 5.14 only apply to BSDI systems.
Red Hat Linux systems don't have a problem with the regex code - it's
something else that's causing the segmentation fault on your system,
so those changes wouldn't have any effect. Did you get more debugging
output before the segmentation fault, though, by using -vvvvvv? If so,
what was it?
> 2. I am going to try htdig-3.2.0b4-010602 src.tgz and see how it works.
I don't expect that will make a difference. The only changes since Oct. 21
were to the internal HTTP transport and cookies support, which you're not
using anyway. However, let us know if this makes a difference.
> 3. I will create a core file with gdb output for your reference if the 2nd
> step still fails.
OK, just please DO NOT send the core file as an attachment, as it would
only be useful on your own system. What we need is the backtrace output
from gdb, whether it comes from a core dump or from running htdig directly
from gdb.
--
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
