https://issues.apache.org/bugzilla/show_bug.cgi?id=54756
--- Comment #6 from Sebb <s...@apache.org> --- (In reply to comment #5) > (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. Indeed. [Sorry, my comment was ambiguous / too terse.] What I meant by the phrase "Ideally, it should not ..." was that JNI code should be defensively written such that the calling Java code cannot cause a crash. > However, since the problem does appear to be in tcnative, one has to > presume it's fixable. Yes, hopefully! -- 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
