Community
Participate
Working Groups
We have a .jar file here (the .jarfile of hell! :-) ), which if listed on a project's classpath causes eclipse to crash - and not only eclipse but apparently even the VM (so maybe this bug should be forwarded to the VM authors - please advise)! I checked this with Sun's VM 1.4.2 and with IBM's VM 1.4.2 - in both cases eclipse dies with the follwing message: --------------------------------- A virtual machine error has occured. You are recommended to exit the workbench. Subsequent errors may happen and may terminate the workbench without warning. See the .log for more details. Do you want to exit the workbench? [Yes] [No] --------------------------------- I can provide the .log file as well as the offending .jar file - just let me know. Michael
If bugzilla would allow me to attach files I would have attached the two right away... Michael
Could you mail these files to me directly ?
From reporter: it seems, that the defect .jar file was created by erroneously checking it into our CVS repository as "ASCII" (instead of binary). So CVS probably replaced CRLF by CR and maybe also any tags (if it found such in the binary file). But of course accessing such a file shouldn't kill the VM... Probably some bug in the native .zip file handling...
We need to add check for error while reading a corrupted zip file.
We cannot catch this case, because it throws an InternalError. We should never catch an InternalError. Closing as a VM bug. See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4615343.