Hi Jos,
Hi C.
It sounds like it crashes on the first file it sees! Does it actually
index any file properly?
Right, I don't think it indexes any file. The only file that is created in
the ~/.strigi/clucene is the segments file.
C.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Hi Jos and Debian Bugzilla,
I've attached output from valgrind after running:
#valgrind xmlindexer kontact.desktop 21valgrindOutput
There are many messages such as
Loading `libextractor_exiv2' plugin failed: libextractor_exiv2.so: cannot
open shared object file: No such file or
Ah, libextractor! that is a problem causer. Please dont use it.
2007/2/26, CSights [EMAIL PROTECTED]:
Hi Jos and Debian Bugzilla,
I've attached output from valgrind after running:
#valgrind xmlindexer kontact.desktop 21valgrindOutput
There are many messages such as
Loading
Hi Jos and Debian bug,
I believe the segfault is caused by some wrongness in the
/usr/lib/strigi/strigita_kfile.so file.
strigi-plugins includes two libraries /usr/lib/strigi/strigita_kfile.so
and /usr/lib/strigi/strigita_libextractor.so .
I get a segfault when I do
#mv
2007/2/23, CSights [EMAIL PROTECTED]:
Hi Jon,
I was able to find that the daemon segfaults on kontact.desktop file. I
discovered which file was causing a segfault by running strigi-daemon under
gdb, then when there was a segfault I checked lsof to find which file
strigi-daemon had
Hi Jon,
I was able to find that the daemon segfaults on kontact.desktop file.
I
discovered which file was causing a segfault by running strigi-daemon under
gdb, then when there was a segfault I checked lsof to find which file
strigi-daemon had opened.
Trying to run
6 matches
Mail list logo