[aseek-devel] Re: Infinite loop in searchd

[Kir Kolyshkin]

Can you subscribe to aseek-devel so we will continue there?

Jens Thoms Toerring wrote:
Hi Kir,

On Tue, Aug 26, 2003 at 04:22:18PM +0359, Kir Kolyshkin wrote:

You should look at ebuf[0], ebuf[1] and pbuf


What can I expect to find in them or how to figue out if they
are supposed to contain?
 
Now I get

(gdb) x/32 ( BYTE * ) p_buf
0x810a068:      0x0001b2b4      0x00009fae      0x0001b2d3      0x00009d9d
0x810a078:      0x0001b2de      0x00009fae      0x0001b2ea      0x00009fda
0x810a088:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a098:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a0a8:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a0b8:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a0c8:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a0d8:      0x00000000      0x00000000      0x00000000      0x00000000
(gdb) x/32 ebuffers[0]
0x810a044:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a054:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a064:      0x000003c1      0x0001b2b4      0x00009fae      0x0001b2d3
0x810a074:      0x00009d9d      0x0001b2de      0x00009fae      0x0001b2ea
0x810a084:      0x00009fda      0x00000000      0x00000000      0x00000000
0x810a094:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a0a4:      0x00000000      0x00000000      0x00000000      0x00000000
0x810a0b4:      0x00000000      0x00000000      0x00000000      0x00000000
(gdb) x/32 ebuffers[1]
0x8108caa:      0x00000000      0x00000000      0x00000000      0x00000000
0x8108cba:      0x00410000      0xdfe00000      0xdfe04023      0x00004023
0x8108cca:      0x00000000      0x00000000      0x00000000      0x00000000
0x8108cda:      0x00000000      0x00000000      0x00000000      0x00000000
0x8108cea:      0x00000000      0x00000000      0x00000000      0x00400000
0x8108cfa:      0x05900000      0xb2b40000      0x00010001      0xb2d30052
0x8108d0a:      0x00030001      0x02550246      0xb2de0263      0x00010001
0x8108d1a:      0xb2ea0052      0x00010001      0xb4730026      0x00010001
But I have now idea at the moment what this is supposed to mean...


Probably your index is broken someway.


Any possibility to check for this? It's a "fresh" index I created
yesterday. But I will try to create a new, smaller one. Of course,
I had to apply quite a bit of changes to 'index' to get it to run.
Did you see anything wrong in what I wrote to you about the changes
I had to make?

BTW on what arch do you run ASPseek?


Linux ub3744 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 unknown

with

[EMAIL PROTECTED]:~> g++ --v
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.2/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib
--enable-languages=c,c++,f77,objc,java,ada --enable-libgcj
--with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib
--enable-shared --enable-__cxa_atexit i486-suse-linux
Thread model: posix
gcc version 3.2
but finally it may end up on

IRIX64 Pfeffer 6.5 07141607 IP27

                             Thanks for your help, Jens


--
== kir_at_asplinux.ru = 7551596_at_ICQ = 6722750_at_sms.beemail.ru ==
I am signature virus. Copy me to your ~/.signature to help me spread.