This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 15882 - HotSpot Virtual Machine Error thrown when starting debugger
Summary: HotSpot Virtual Machine Error thrown when starting debugger
Status: CLOSED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: PC Other
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-25 10:52 UTC by npierpoint
Modified: 2001-10-04 11:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Full thread dump (12.19 KB, text/plain)
2001-09-25 10:57 UTC, npierpoint 		Details
IDE log file (15.54 KB, text/plain)
2001-09-25 10:59 UTC, npierpoint 		Details
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 npierpoint 2001-09-25 10:52:47 UTC 
A web application that I could debug with no problem in Forte 2.0, now crashes 
spectacularly when I try to debug it in Forte 3.0.

The following unhelpful error is thrown and the Debugger finishes.

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 5052455345525645255843455054494F4E0E4350500024
#
# Problematic Thread: prio=5 tid=0x7c52b0 nid=0x169 runnable 
#
Comment 1 npierpoint 2001-09-25 10:57:58 UTC 
Created attachment 2681 [details]
Full thread dump
Comment 2 npierpoint 2001-09-25 10:59:47 UTC 
Created attachment 2682 [details]
IDE log file
Comment 3 Jan Stola 2001-09-26 11:15:08 UTC 
Unfortunately we can't do anything with this bug.
It can't be bug in our code. It seems to be bug in JDK.
See for example following bug report against JDK
(it looks similar to your problem):
http://developer.java.sun.com/developer/bugParade/bugs/4362206.html
Comment 4 timbell 2001-10-03 22:17:22 UTC 
Workaround:

If your debugging session is crashing with this error,
If running with the 1.3.1 SDK, the workaround (on win32
and on Linux) is to use the "Classic" VM.  Add "-classic"
to the command line used to start your debugee program.
Comment 5 Jan Stola 2001-10-04 11:31:00 UTC 
Wontfix -> Closed.