I took my first swing at integrating mod_mbox and Lucene4c this
afternoon. Code wise, it all worked. However, running the code, I
quickly ran into a problem:
#0 0x40268e38 in _Unwind_Find_FDE () from /lib/tls/libc.so.6
#1 0x402678a5 in dl_iterate_phdr () from /lib/tls/libc.so.6
#2 0x40268925 in _Unwind_Find_FDE () from /lib/tls/libc.so.6
#3 0x411987ef in uw_frame_state_for (context=0xbfbc41e0, fs=0xbfbc4120)
at ../../gcc-4.0.0/gcc/unwind-dw2.c:971
#4 0x41199cbc in _Unwind_RaiseException (exc=0x5429e0) at unwind.inc:104
#5 0x408611e2 in _Jv_Throw (value=0x2967e0) at
../../../gcc-4.0.0/libjava/exception.cc:103
#6 0x40854afa in catch_segv (_dummy=11) at
../../../gcc-4.0.0/libjava/prims.cc:152
#7 <signal handler called>
#8 0x41198b1d in uw_frame_state_for (context=0xbfbc4718, fs=0xbfbc4658)
at linux-unwind.h:125
#9 0x41199cbc in _Unwind_RaiseException (exc=0x542a20) at unwind.inc:104
#10 0x408611e2 in _Jv_Throw (value=0x2967f8) at
../../../gcc-4.0.0/libjava/exception.cc:103
#11 0x40854afa in catch_segv (_dummy=11) at
../../../gcc-4.0.0/libjava/prims.cc:152
#12 <signal handler called>
#13 0x41198b1d in uw_frame_state_for (context=0xbfbc4c50, fs=0xbfbc4b90)
at linux-unwind.h:125
#14 0x41199cbc in _Unwind_RaiseException (exc=0x542a60) at unwind.inc:104
#15 0x408611e2 in _Jv_Throw (value=0x296810) at
../../../gcc-4.0.0/libjava/exception.cc:103
#16 0x40854afa in catch_segv (_dummy=11) at
../../../gcc-4.0.0/libjava/prims.cc:152
#17 <signal handler called>
...continues forever...
More or less, java is catching a signal, and then causing another signal
to be sent from inside the handler (ouch!). This seems to happen
randomly while adding thousands of documents to a writer.
Source is at:
http://svn.apache.org/repos/asf/httpd/mod_mbox/trunk/module-2.0/mbox_search.c
It seems this is likely a bug in gcj?
-Paul
afternoon. Code wise, it all worked. However, running the code, I
quickly ran into a problem:
#0 0x40268e38 in _Unwind_Find_FDE () from /lib/tls/libc.so.6
#1 0x402678a5 in dl_iterate_phdr () from /lib/tls/libc.so.6
#2 0x40268925 in _Unwind_Find_FDE () from /lib/tls/libc.so.6
#3 0x411987ef in uw_frame_state_for (context=0xbfbc41e0, fs=0xbfbc4120)
at ../../gcc-4.0.0/gcc/unwind-dw2.c:971
#4 0x41199cbc in _Unwind_RaiseException (exc=0x5429e0) at unwind.inc:104
#5 0x408611e2 in _Jv_Throw (value=0x2967e0) at
../../../gcc-4.0.0/libjava/exception.cc:103
#6 0x40854afa in catch_segv (_dummy=11) at
../../../gcc-4.0.0/libjava/prims.cc:152
#7 <signal handler called>
#8 0x41198b1d in uw_frame_state_for (context=0xbfbc4718, fs=0xbfbc4658)
at linux-unwind.h:125
#9 0x41199cbc in _Unwind_RaiseException (exc=0x542a20) at unwind.inc:104
#10 0x408611e2 in _Jv_Throw (value=0x2967f8) at
../../../gcc-4.0.0/libjava/exception.cc:103
#11 0x40854afa in catch_segv (_dummy=11) at
../../../gcc-4.0.0/libjava/prims.cc:152
#12 <signal handler called>
#13 0x41198b1d in uw_frame_state_for (context=0xbfbc4c50, fs=0xbfbc4b90)
at linux-unwind.h:125
#14 0x41199cbc in _Unwind_RaiseException (exc=0x542a60) at unwind.inc:104
#15 0x408611e2 in _Jv_Throw (value=0x296810) at
../../../gcc-4.0.0/libjava/exception.cc:103
#16 0x40854afa in catch_segv (_dummy=11) at
../../../gcc-4.0.0/libjava/prims.cc:152
#17 <signal handler called>
...continues forever...
More or less, java is catching a signal, and then causing another signal
to be sent from inside the handler (ouch!). This seems to happen
randomly while adding thousands of documents to a writer.
Source is at:
http://svn.apache.org/repos/asf/httpd/mod_mbox/trunk/module-2.0/mbox_search.c
It seems this is likely a bug in gcj?
-Paul