Good news! I was able to succesfully run multithreaded index (and searchd) on FreeBSD 4.4. The problems we observed with index was SIGSEGV while running under gdb, and endless loop in _thread_sigframe_restore() while running stand-alone. Investigation found that values of some variables passed as function and method arguments are corrupted, and that stack size is only 128 kb per thread. Raising it to 1 Mb helped a lot, now I run index -N 4 for one our without a failure.
My setup: aspseek - 1.2.9pre (latest from CVS) $ uname -mrv 4.4-20010827-RC2 FreeBSD 4.4-20010827-RC2 #1: Thu Aug 30 22:15:52 MSD 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/xxxx i386 $ gcc -v Using builtin specs. gcc version 2.95.3 20010315 (release) [FreeBSD] John, can you checkout and test latest cvs? John Capo wrote: > > My attempts to debug this have pretty frustrating. I have never > had a segv in the same place. About 50% of the time the segv > happens in one of the functions/macros/whatever in the stl_* include > files. > > I do have a new data point for this problem. I compiled both 1.2.4a > and 1.2.5 without unicode support and both versions ran for several > hours with 25 threads without a segv. At some point both versions > hung and would only respond to kill -9. Also, a "word -otherword" > query appears to be broken without unicode support. > > John Capo > IRBS Engineering, Inc. > > Quoting Kir Kolyshkin ([EMAIL PROTECTED]): > > Can you debug it with gdb and see what happens? > > > > Denis Mysenko pisal(a): > > > > > > Thanks, it works. > > > But I got another trouble :) > > > When I run index -N >1 (with same -R) I start getting > > > following output (after minute or few): > > > > > > ... > > > Address of param: bf8b96b8 > > > Address of param: bf8b8074 > > > Address of param: bf8b96b8 > > > Address of param: bf8b8074 > > > ... > > > > > > After another minute or few process hangs. > > > I tryed aspseek1.2.4a and 1.2.5 on FreeBSD 4.3-STABLE. > > > > > > On Wed, 24 Oct 2001, Kir Kolyshkin wrote: > > > > > > > Denis Mysenko pisal(a): > > > > > > > > > > Hello. > > > > > I'm sure my question is being asked not for first time but I couldn't > > > > > find anything useful in mail listing archive. > > > > > > > > > > I added "Include charsets.conf" to the aspseek.conf and searchd.conf files > > > > > (there are only ucharset.conf by default) and removed "Include > > > > > ucharset.conf". I guess I'm not forced to use Unicode in order to have > > > > > multi-language support? All my sites are english/russian. > > > > > Russians words appear correctly in MySQL tables and search results when > > > > > query contains only english words. > > > > > > > > > > When I search for russian word(s) I get "search returned no results". > > > > > Any ideas? > > > > > > > > Recompile aspseek with ./configure --disable-unicode > > > > You can see the list of available options by running > > > > ./configure --help > > > > > > > > -- > > > > [EMAIL PROTECTED] ICQ 7551596 Phone +7 903 6722750 > > > > Reality always seems harsher in the early morning. > > > > -- > > > > > > > > > > -- > > > Denis Mysenko > > > Siberian Internet Company > > > +7 382 2420471 > > > > -- > > [EMAIL PROTECTED] http://kir.vtx.ru/ ICQ 7551596 Phone +7 903 6722750 > > I am a .signature virus. Copy me to your .signature to help me spread. > > -- -- [EMAIL PROTECTED] http://kir.vtx.ru/ ICQ 7551596 Phone +7 903 6722750 Hi, I'm a signature virus: copy me to your .signature to help me spread! --
