[pylucene-dev] seqfault in KeywordAnalyzerTest with jcc-enabled PyLucene

[Andi Vajda]

On Fri, 30 Nov 2007, Felix Schwarz wrote:

> I'm using CentOS 5 (x86) with Python 2.4 and Sun JDK 1.6 u3. After installing
> JCC from trunk (r369), I compiled pylucene with jcc (r369). After doing
> 'make install' as root, I issued 'make test' (as ordinary user).
>
> everything runs fine until KeywordAnalyzerTest is executed:
>
> /usr/bin/python samples/LuceneInAction/KeywordAnalyzerTest.py
> ..#
> # An unexpected error has been detected by Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00171e72, pid=14197, tid=1073804624
> #
> # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode, sharing)
> # Problematic frame:
> # C  [libpython2.4.so.1.0+0x70e72]  PyUnicodeUCS4_FromUnicode+0x92
> #
> # An error report file with more information is saved as hs_err_pid14197.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> xargs: /usr/bin/python: terminated by signal 6
> make: *** [test] Error 125
>
>
> The seqfault seems to be in testSimpleKeywordAnalyzer() before:
> self.assertEqual(ts.next().termText(), input)
> The program terminates immediately after ts.next().

Could it be that there is a mismatch in unicode char width between the 
python you compiled PyLucene with and the python you're running it with 
(which should be the same, really) ?

>From the name of the function on the stack 'PyUnicodeUCS4_FromUnicode', it 
could imply this.

To debug this, use gdb. You can recompile PyLucene with DEBUG=1 to disable 
optimizations and get a better gdb experience.

Andi..