Quite possibly. Does 'make test' succeed ?
Not entirely; everything works except for test_PythonDirectory and
test_RangeFilter, which both segmentation fault. The stack trace goes
like this:
#0 0xb7d48adf in sigprocmask () from /lib/tls/libc.so.6
#1 0xb6d3ce38 in _Jv_SetInitialHeapSize ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgcj.so.7
#2 0xb6d3d5e0 in _Jv_ThrowBadArrayIndex ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgcj.so.7
#3 <signal handler called>
#4 0xb7368a00 in GC_local_gcj_malloc ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgcj.so.7
#5 0xb6d3d3ca in _Jv_AllocObjectNoFinalizer ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgcj.so.7
#6 0xb6d3d436 in _Jv_AllocObject ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgcj.so.7
#7 0xb6d3d5f9 in _Jv_ThrowBadArrayIndex ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgcj.so.7
And then lines 3-7 repeat forever, same thing for both tests. I've
never seen such a deep stack trace. Anyhow, I guess I'll complain to
the gcj people if the linked patch doesn't fist this, and if I can find
a better way to report the error. Do you have any idea why PyLucene's
make test isn't part of the standard testing procedure for the gcj
team? It seems like one of the better tests of whether the compiler is
functional in a given configuration.
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
