Bug 75503 - [VM] crash in Scanner.getCurrentIdentifierSource()
Summary: [VM] crash in Scanner.getCurrentIdentifierSource()
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.1 M4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: vm
Depends on:
Blocks:
 
Reported: 2004-10-01 17:15 EDT by Zach Lute CLA
Modified: 2005-02-16 09:40 EST (History)
0 users

See Also:

Attachments
Full log of error from JVM (45.15 KB, text/plain)
2004-10-01 17:16 EDT, Zach Lute CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zach Lute CLA 2004-10-01 17:15:15 EDT 
This is very similar to Bug #57141 except that it occurs in the Sun JDK 1.5.0
final release instead of that bug, which seems to no longer occurs, so I assume
they're probably somehow related.

The output at the console follows, and I'm going to attach the full hotspot log
in case it will be of any use.

-----

Unhandled event loop exception
Reason:
java.lang.NullPointerException
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x0000002a99e979ce, pid=9839, tid=1104922976
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-b64 mixed mode)
# Problematic frame:
# J  org.eclipse.jdt.internal.compiler.parser.Scanner.getCurrentIdentifierSource()[C
#
# An error report file with more information is saved as hs_err_pid9839.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Comment 1 Zach Lute CLA 2004-10-01 17:16:29 EDT 
Created attachment 14955 [details]
Full log of error from JVM
Comment 2 Zach Lute CLA 2004-10-01 17:24:28 EDT 
I should also note that while the log is from a crash of Eclipse 3.1M2, the same
exact thing occurred while using the 3.0.1 release and I merely updated to see
if it had been fixed already.
Comment 3 Philipe Mulet CLA 2004-10-01 19:14:26 EDT 
This is a VM bug. You should report it to VM vendor, or turn the JIT off.
Comment 4 Olivier Thomann CLA 2004-12-13 21:30:47 EST 
Closing as WORKSFORME.