strigicmd crashes due to old libclucene0 bug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
clucene-core (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
A bug in libclucene0 that was fixed [1] long ago causes strigicmd to crash.
It would be best to update to the latest stable release (0.9.21b) but adding the patch below suffices too.
The crash (segmentation fault) can be obtained by running e.g.
mkdir /tmp/clucene
valgrind strigicmd create -t clucene -j 1 -d /tmp/clucene $HOME
It might take a while for the crash to happens which is why running with valgrind is good: it shows the memory corruption [3] quickly.
This problem exists in jaunty and karmic [2].
[1] http://
diff -r clucene-
81c81
< if(bufferTextLe
---
> if(bufferTextLe
[2]
libclucene0ldbl:
Installed: 0.9.20-3
Candidate: 0.9.20-3
Version table:
*** 0.9.20-3 0
500 http://
100 /var/lib/
libclucene0ldbl:
Installed: 0.9.20-3
Candidate: 0.9.20-3
Version table:
*** 0.9.20-3 0
500 http://
100 /var/lib/
==2065== Invalid read of size 4
==2065== at 0x599DB90: wcslen (wcslen.c:30)
==2065== by 0x7024B4B: lucene:
==2065== by 0x7037D44: lucene:
==2065== by 0x7038007: lucene:
==2065== by 0x7038DD2: lucene:
==2065== by 0x7037B1E: lucene:
==2065== by 0x70349ED: lucene:
==2065== by 0x7034542: lucene:
==2065== by 0x703FFAD: lucene:
==2065== by 0x704077E: lucene:
==2065== by 0x704A9E1: lucene:
==2065== by 0x6D9ED4C: CLuceneIndexWri