Hello Geoff,
At 19:25 05-03-01 -0600, Geoff Hutchison wrote:
>At 10:21 PM +0100 3/4/01, Tjerk Vonck wrote:
>>It took us some testing and hefty logging to find out a simple search for
>>'a b' triggers the problem. With this search, very reproducable, within
>>seconds load average starts to grow from 0.02 on average to 0.7, 1.5, 2.x
>>and soon going sky-high while grabbing 99.9% CPU and eating swap like a
>>carnivore.
>
>Can you reproduce it with words that match the minimum_world_length?
No. We use the default minimum_world_length of 3. As I wrote in my previous
email searches in which the words all match the minimum word length give no
problems.
Searches for words like a and b or aa and bb lead to troubles.
>>--without-zlib" after which this step was repeated with the --without-zlib
>>option. After that we compiled and installed htdig without any problems.
>
>I'm a little worried that the wordlist compression code isn't always
>turned off completely, so this may or may not be the culprit. Would
>you be willing to install zlib and recompile?
sure, I'll get back on this later!
>Can you get this same bug when running htsearch from the command-line?
Yup, with interesting results! After the 'Enter value for words:' question
is asked and answered with 'a b' for instance, we never get to the 'Enter
value for format:' question! I have to kill -9 the process...
I assume that means we never reach the actual search?
>If so, you can get some information when running strace
>or gdb. If you don't know how to use these, we can offer tips.
Yup I can run both strace and gdb but I'm totally unexperienced there. What
options would you like me to use? (be detailed?)
Tjerk.
_______________________________________________
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
