Re: glimpseindex

1999-09-15 Thread Keith Harbaugh
On Mon, 1999-09-13 18:03:35 +0100, Martin Oldfield wrote:
 I thought I'd give glimpse a whirl to index a bunch of email archives, 
 but I get a segmentation fault:
 
 
 % glimpseindex -o -B archive
 
 This is glimpseindex version 4.1, 1997.
 
 Indexing /home/mjo/adamsarch/archive ...
 
 
 Size of files being indexed = 172104723 B, Total #of files = 26801
 Segmentation fault
 
 
 The BTS seems to have similar problems already e.g. bug 20037 but no
 obvious solution. I'm running version 4.1-2 which seems to be the most 
 recent.
 
 Has anyone else been down this path before, and did they find a
 solution ?
 
 Cheers,
 -- 
 Martin Oldfield,

I had success with just `glimpseindex -o'.
Caveats:
1) The working directory was ~/Mail.
2) Under that, there were a large number (~30) of subdirectories,
   each in maildir format (i.e., each had a new, cur and tmp directory,
   with the email being held one message to a file under cur).
3) The result was to place eight .glimpse... files in ~,
   but then glimpse worked just as documented to search them.
4) Also running version 4.1-2 on a slink system (but with linux 2.2.12).

Good luck,
Keith


Re: glimpseindex

1999-09-15 Thread Martin Oldfield
Thanks for your note. I tried glimpseindex -o but got the same
error. gdb gives this stack trace:

Program received signal SIGSEGV, Segmentation fault.
0x4004f848 in free ()
(gdb) where 
#0  0x4004f848 in free ()
#1  0x4004f7f1 in free ()
#2  0x804eaf0 in my_free ()
#3  0x8052802 in build_hash ()
#4  0x80502a1 in build_index ()
#5  0x804acf5 in main ()
(gdb) 

And the source (.../index/build_in.c) has this little gem:

build_hash();
/* traverse1(); ZZ removed on oct/8/96, 
bgopal, to see if crazysegvs disappear on lec

As a workaround this appears to work:

glimpseindex -B -b archive

Sadly the more recent versions of the code seem to be harder to get
to, unless you're an educational sort.

Cheers,
-- 
Martin Oldfield,