Java Result: 139

Hi,

I'm using a C library to read a special format files. It works great for small files, a few MB, but when reading bigger files, 50MB is enough, it crashes simply outputting:

Java Result: 139

Anyone as a clew on what a Java Result: 139 is? or where I can get Java Results description? I searched the "entire" web and found very few references to Java Results.

Best regards,

Carola.

[423 byte] By [Carolaa] at [2007-10-2 23:09:20]
# 1

It probably doesn't matter what it means.

The problem is probably in the C library and has nothing to do with java. You could write a C executable and test this.

Possibly either the C library just won't handle that or there is some configuration you need to set for it.

There is a possibility that you can try altering the stack size. If that works you might want to consider long term what a real solution is (because increasing the stack size to handle bigger files probably is going to stop working after a while.)

jschella at 2007-7-14 6:23:15 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 2

Thanks for the reply,

I had allready tested the library with a C executable, it works fine. The problem must be with java because I read all the data correctly the crash occurs while setting the object fields.

But shouldn't the result tell me something? someone decided to output numbers did they forgot to document its meaning?

I had allready tryed increasing the stack size, but lack of stack would result in outofmemoryexception, I checked it by reducing it.

I guess the safest will be to change the loading process. But if anyone has any information on Java results I would still apreciate it because I have a few more using the JNI Wrapper for VTK.

Best regards,

Carola.

Carolaa at 2007-7-14 6:23:15 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 3
Hi, Have you tried with generic JNI wrappers ?You can test for free some commercial products to see if they work, and ask for support if they don't.You can also try free ones like JNative.--Marc ( http://jnative.sf.net)
mdentya at 2007-7-14 6:23:15 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 4

> Thanks for the reply,

> I had allready tested the library with a C

> executable, it works fine. The problem must be with

> java because I read all the data correctly the crash

> occurs while setting the object fields.

Then that strongly suggests that the problem is in your JNI code.

jschella at 2007-7-14 6:23:15 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 5
That probably means exit codeand 139 means 128 + 11 where 11 is SIGSEGV I would suggest to run your application with '-Xcheck:jni' and see if there are any complains.-katya
ekatermaa at 2007-7-14 6:23:15 > top of Java-index,Java HotSpot Virtual Machine,Specifications...