According to Rob Kremer: > When I reach a document that has restricted access, the connection is closed and > then HtDig core dumps on the next file it tries to access. > > Obviously, HtDig can't index files it doesn't have access to, but I wouldn't > expect it to core dump on the next file. > > I am doing something wrong, is this a bug, is there a way I can get around it > without excluding all of the files I don't have access to? ... > Solaris 2.6, htdig-3.2.0b4-20021020 ... > Making HTTPS request on > https://myhost/cel/inv/work_area/website/WK000887/rt_proc_entry.html > Try to get through to host myhost (port 443) > 23 - Open of the connection ok > Assigning the server (myhost) to the TCP connection > Assigned the remote host myhost > Assigning the port (443) to the TCP connection > Assigned the port 443 > Connecting via TCP to (myhost:443) > Segmentation Fault - core dumped > + [ 139 != 0 ] > + exit
If you could provide a gdb stack backtrace showing exactly where htdig was executing when it got the segmentation fault, that would be a big help. Sounds like a pointer bug in the https handling code, but it would be nice to narrow it down further than that. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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
