[pylucene-dev] Re: seqfault in KeywordAnalyzerTest with
felix.schwarz at oss.schwarz.eu
Fri Nov 30 08:45:48 PST 2007
Andi Vajda wrote:
>> 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) ?
How can I check this?
I'm just using the Python which comes with CentOS 5 and did not modify
anything in PyLucene (besides some Makefile/setup.py stuff).
>> 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.
Thank you very much.
More information about the pylucene-dev