JDK-4326445 : NSK regression test b4254544 causes Internal Error
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 1.3.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_7
  • CPU: sparc
  • Submitted: 2000-03-30
  • Updated: 2016-05-09
  • Resolved: 2000-04-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.0 solarisFixed
Related Reports
Relates :  
Relates :  
Relates :  
Description

Name: dkC59003			Date: 03/30/2000


Kestrel HotSpot Server build Solaris_JDK_1.3-b08 fails the test 
nsk/regression/b4254544 from testbase_nsk.

The test inserts HashMap into itself which crashes VM.

This happens only for -server option, -hotspot works OK as well as
java_g -server.

To reproduce the bug run
doit <jdk root directory> -server
in
/net/sqesvr/vsn/GammaBase/Bugs/<this bug number>

The test produces the output:

$ doit /export/ld24/java/hotspot/Solaris_JDK_1.3-b08 -server
java version "1.3"
Java(TM) 2 Runtime Environment, Standard Edition (build Solaris_JDK_1.3-b08)
Java HotSpot(TM) Server VM (build 1.3, mixed mode)
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 53484152454432554E54494D450E4350500152 01
#
# Problematic Thread: prio=5 tid=0x27ed8 nid=0x1 runnable 
#

(Error ID: sharedRuntime.cpp, 338)

======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: kestrel-solaris INTEGRATED IN: kestrel-solaris VERIFIED IN: mantis
14-06-2004

EVALUATION If the code blob which actually causes the stack overflow (yellow zone hit) is a C2I adapter, the VM panics, because it does not expect adapters to raise exceptions. Solution is to teach the VM that adapters have no exception handlers, and should just pop to their callers. I have adjusted the assertion checks so that the VM is "broadminded" about exceptions in adapters only when queried from the stack overflow handler stub. john.rose@Eng 2000-03-31
31-03-2000