> Segfault when indexing or searching?
Whenever the swish-e binary is executed, indexing,
searching, help switch, version, etc.
> 1) find the smallest smallest input document or documents that can be
> used to create the problem --
A file with the sentence "The quick brown fox jumped over the lazy dog."
was indexed and that index was searched using the switches '-w "lazy" -f
> 2) use gdb to find out where the segfault is happening.
Unfortunately I don't have any debugging experience, but below is the
backtrace of the search.
Starting program: /usr/local/bin/swish-e -w "lazy" -f index_test.idx
[New Thread 1075397248 (LWP 2945)]
# SWISH format: 2.4.0
# Search words: lazy
# Removed stopwords:
# Number of hits: 1
# Search time: 0.002 seconds
# Run time: 0.060 seconds
1000 index_test.txt "index_test.txt" 47
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1075397248 (LWP 2945)]
0x420734c1 in free () from /lib/tls/libc.so.6
#0 0x420734c1 in free () from /lib/tls/libc.so.6
#1 0x420eb85e in __unregister_atfork () from /lib/tls/libc.so.6
#2 0x42029eae in __cxa_finalize () from /lib/tls/libc.so.6
#3 0x4012611c in __do_global_dtors_aux () from
#4 0x40149c76 in _fini () from /usr/local/lib/libswish-e.so.2
#5 0x4000c894 in _dl_fini () from /lib/ld-linux.so.2
#6 0x42029c20 in exit () from /lib/tls/libc.so.6
#7 0x0804bcb0 in main (argc=5, argv=0xffffffff) at swish.c:232
#8 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6
Received on Sat Nov 8 21:09:35 2003