On Tue, 27 Feb 2001, Alexander Cohen wrote:
> #0 0x1200950f0 in List::Destroy (this=0x11fffe858) at List.cc:82
> #1 0x120094fd8 in List::~List (this=0x11fffe858, __in_chrg=2) at List.cc:48
> #2 0x120099a28 in HtRegexList::~HtRegexList (this=0x11fffe858, __in_chrg=2) at
> HtRegexList.cc:38
> #3 0x12003bd78 in Retriever::IsValidURL (this=0x11ffff200, u=@0x141003c40) at
> Retriever.cc:990
Well, I certainly know what the culprit is, but it's something I tried to
test pretty thoroughly. I'll go through the HtRegexList class more
thoroughly.
In the meantime, you can solve this problem by going into
HtRegexList::match() and commenting out everything inside the statement:
if (cursor.current_index != -1)
{
// comment all this out
}
This will prevent the HtRegexList from rearranging. It won't be as fast as
it might be, but it certainly won't segfault. :-)
-Geoff
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
