Check doc/bugs.txt. It explains how to post crashes reports. > hi, > > i got several problems with mnoGoSearch. > > Currently i'm trying to use version 3.1.11 on a regular linux box. I > already tried on different linux machines, so its not a problem of > hardware, distribution or something like that. > > I was using 3.1.8 before. I've got a mysql-database with something > around 500.000 urls in it. I've seen that the layout of the > servertable changed (proxy_port). > > If a say "-q" (do not add server URLs), it runs well. > > The same problem with version 3.1.8. > > strace says (after reading the stopwords from the table): > > write(4, "!\0\0\0\3SELECT hostinfo,path FROM r"..., 37) = 37 > > then a few rows get read, looking like this: > > read(4, "\20www.kostenlos.de\v/search.htm", 29) = 29 > read(4, "\33\0\0h", 4) = 4 > read(4, "\20www.kostenlos.de\t/cgi-bin/", 27) = 27 > read(4, "!\0\0i", 4) = 4 > read(4, "\20www.kostenlos.de\17/aktuelles_txt"..., 33) = 33 > read(4, "\31\0\0j", 4) = 4 > read(4, "\20www.kostenlos.de\7/forum/", 25) = 25 > read(4, "\1\0\0k", 4) = 4 > read(4, "\376", 1) = 1 > brk(0x8096000) = 0x8096000 > time([983155429]) = 983155429 > time([983155429]) = 983155429 > +++ killed by SIGSEGV +++ > > ^.. here we have the segfault then. > > Even with an empty robots-table the problem stays with me :/ > > I sent a mail with the same description to the developers some month > ago. Because there was a new version out, i thought that it might has > been fixed. > > I can't keep the index uptodate, and i had to stop the project where > mnoGoSearch should be used for. Now its really time for me to get it > back online, so i'm trying my luck with the mailinglist right now. > > If someone has an idea, how to solve that problem, please let me know. ___________________________________________ If you want to unsubscribe send "unsubscribe general" to [EMAIL PROTECTED]
