Where can i get the debug build?

On Wed, Jul 16, 2008 at 2:29 PM, Timothy Wall <twal...@dev.java.net> wrote: Run against a debug build of jna and you might get more native stack information.

Other than that, it looks like memcpy is getting passed a bad pointer.

On Jul 16, 2008, at 4:38 AM, evgeni shafran wrote:

i have multi thread daemon using JNA which frequently crashes with the folowing error (full dump attached):

# # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00000034c36723bc, pid=14041, tid=1093912928 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b22 mixed mode linux-amd64) # Problematic frame: # C [libc.so.6+0x723bc] memcpy+0x1c # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --------------- T H R E A D --------------- Current thread (0x0000002adcb37000): JavaThread "Thread-5" daemon [_thread_in_native, id=14119, stack(0x000000004123c000,0x000000004133d000)] siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000002ae3c7b675

The daemon uses FFMPEG library (libavcodec) through Java-FFMPEG bindings, which in turn use JNA.

I need any way to either solve the issue, or to isolate the crashing thread and not allow the crash to propogate to the rest of the daemon.

Please assist, I'm trying to solve this for the entire last week.

If the source code required, any tips of locating the offending FFMPEG C++ function would be appreciated (currently, as you see, it only shows the point of crash but not the c++ functions stack).

Thanks to anyone who will reply. < hs_err_pid14041 .log

To unsubscribe, e-mail: user...@jna.dev.java.net For additional commands, e-mail: user...@jna.dev.java.net