Segmentation Fault on Solaris JVM

Question

Hi,
We have a Java application that executes all 'C' code through JNI code.
It works fine on NT but on solaris, the JVM suddenly crashes with a
segmentation fault. The crashes are random. We did a lot of debugging to ensure that the JVM doesn't crash when we are in the 'C' code.
We are using jdk1.4.0-b92. Any ideas?
Here's the stack trace from gdb:
Program received signal SIGSEGV, Segmentation fault.
0xfa535000 in ?? ()
(gdb) bt
#0 0xfa535000 in ?? ()
#1 0xfa53908c in ?? ()
#2 0xfa538f50 in ?? ()
#3 0xfa534480 in ?? ()
#4 0xfa52d560 in ?? ()
#5 0xfa405c54 in ?? ()
#6 0xfa405b88 in ?? ()
#7 0xfa405da8 in ?? ()
#8 0xfa405da8 in ?? ()
#9 0xfa405da8 in ?? ()
#10 0xfa400440 in ?? ()
#11 0xfe0fd9ac in __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ ()
#12 0xfe10f644 in __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ ()
#13 0xfe10f4a4 in __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ ()
#14 0xfe10f42c in __1cMthread_entry6FpnKJavaThread_pnGThread__v_ ()
#15 0xfe10f13c in __1cKJavaThreadDrun6M_v_ ()
#16 0xfe0fc284 in _start ()

Answer 1

I had same segmentation fault and found out some char array variable's value length is over the size of char array variable. After fixed it, then it doesn't have that segmentation fault.
In Solaris, when I use java JFileChooser to select a file, the file path usually including a lot of "../" which causes a path over 200 char long. When I assigned that path to a char array variable which only have 200 char length, the segmentation fault happened.