https://issues.apache.org/bugzilla/show_bug.cgi?id=54756
--- Comment #5 from Chuck Caldarale <chuck.caldar...@unisys.com> --- (In reply to comment #4) > Ideally, it should not be possible to crash the JVM - whether that is by > bugs in the JVM native code or in user-provided JNI code as is the case here. Unfortunately, that's not true. Native code invoked by JNI has full access to the memory of the process, so it can scribble all over the Java heap, C heap, the stack of any thread, or any other writable bits and pieces. Get a bit of pointer arithmetic wrong or make use of a dead object and it's game over. However, since the problem does appear to be in tcnative, one has to presume it's fixable. This particular problem is attempting to read from address 0x0000000000000040, so I'm guessing the native code picked up a null pointer to something and is trying to look at offset 0x40 within the structure. Since this is using the relatively new WebSocket capability with APR, I would suspect some timing issue in socket handling. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
