[pylucene-dev] "terminate called after throwing an instance of 'JCCEnv::exception'"

Andi Vajda vajda at osafoundation.org
Thu Jul 17 13:46:58 PDT 2008


On Thu, 17 Jul 2008, Bill Janssen wrote:

>> If you can be more specific about the error, there probably is a way to
>> catch that particular instance of the exception.
>
> Here's the exception:
>
> Exception in thread "main" java.lang.IllegalArgumentException: Unknown image type 0

And no stacktrace ?
I guess it's time to reproduce this under gdb. When the exception hits, gdb 
picks up and you can get a stacktrace. It's a good idea to add '-O0', '-g' 
to your CFLAGS (in jcc's setup.py) and to remove -Wl,-S from your LFLAGS 
first. Rebuild JCC and your eggs, then restart under gdb.

Andi..

>
>> It's a known issue that there are some cases where these exceptions are not
>> caught. It's somewhat hard to get them all. It's usually at startup time
>> that these uncaught exceptions happen, typically when a class is not found
>> (normally, a classpath error).
>
> This happens well after startup.
>
> Bill
>


More information about the pylucene-dev mailing list