bad class file crash the VM
Rémi Forax
forax at univ-mlv.fr
Tue Jan 4 17:30:58 PST 2011
On 01/05/2011 01:31 AM, John Rose wrote:
> On Jan 2, 2011, at 6:42 AM, Rémi Forax wrote:
>
>> This means there is a bug in my code but also
>> that there is a bug in the VM which should reject the bad class file
>> instead of crashing.
> Try "java -Xverify:all". If the class file fails verification *but* the verifier is not used, the JVM is allowed to be unpredictable.
>
> -- John
The class file is verified :(
[forax at localhost tmp]$ java -XX:+UnlockExperimentalVMOptions
-XX:+EnableInvokeDynamic -Xverify:all IndyTest
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00a68ef7, pid=26924, tid=1444720
#
# JRE version: 7.0-b123
# Java VM: Java HotSpot(TM) Server VM (20.0-b04 mixed mode linux-x86 )
# Problematic frame:
# V [libjvm.so+0x32eef7] JavaThread::last_frame()+0xa7
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid26924.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)
Rémi
PS: I've put the hotspot error log as attachment
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hs_err_pid26924.log
Url: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20110105/b65f4fa1/attachment-0001.ksh
More information about the mlvm-dev
mailing list