J
Jayaram
I have a JAVA server program that makes JNI calls to a 'C' shared
library on HP-UX. The 'C' shared library has been compiled using the
'-g' option. However, I notice that if for any reason the JAVA Server
dumps core due to a problem with the 'C' code, standard debuggers like
'gdb' report the core file created as being corrupt.
How does one normally debug core files created by the JNI code ?
Thanks,
Jayaram
library on HP-UX. The 'C' shared library has been compiled using the
'-g' option. However, I notice that if for any reason the JAVA Server
dumps core due to a problem with the 'C' code, standard debuggers like
'gdb' report the core file created as being corrupt.
How does one normally debug core files created by the JNI code ?
Thanks,
Jayaram