JDK-4522770 : Reg-test JITDebug.java Failing
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_98
  • CPU: x86
  • Submitted: 2001-11-05
  • Updated: 2002-03-19
  • Resolved: 2002-03-08
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.4.1 hopperFixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Description

Name: as83306			Date: 11/05/2001

Regression test com/sun/jdi/JITDebug.java fails with Merlin 
build 84 on win98, host cwbybkr.  This bug also existed in Ladybird # 4422312

 For test hardware config's, see http://sqesvr.eng/st3/jdk1.4/docs/Merlin-hw.html
#Test Results (version 2)
#Wed Oct 24 14:27:15 PDT 2001
#checksum:2a48e625e4273f8c
#-----testdescription-----
$file=X:\\st1\\regression\\merlin\\jdk1.4Tests\\tests\\b84\\com\\sun\\jdi\\JITDebug.jav
a
$root=X:\\st1\\regression\\merlin\\jdk1.4Tests\\tests\\b84
author=Robert Field
keywords=bug4291701 othervm
run=USER_SPECIFIED main/othervm JITDebug\r\n
source=JITDebug.java
title=Test JIT debugging -  assure that launching on uncaught exception works

#-----environment-----

#-----testresult-----
description=file:///X:/st1/regression/merlin/jdk1.4Tests/tests/b84/com/sun/jdi/JITDebug
.java
end=Wed Oct 24 14:27:15 PDT 2001
environment=regtest
execStatus=Failed. Execution failed: Program `C:/Java/jdk14b84\\bin\\java' interrupted! 
(timed out?)
javatestOS=Windows 98 4.10 (x86)
javatestVersion=2.1.5
script=com.sun.javatest.regtest.RegressionScript 
sections=script_messages build compile main
start=Wed Oct 24 14:25:13 PDT 2001
status=Failed. Execution failed: Program `C:/Java/jdk14b84\\bin\\java' interrupted! 
(timed out?)
test=com/sun/jdi/JITDebug.java
work=C:\\Results\\Regression\\merlin\\b84\\CWBYBKR-Windows_98-jth13-jdk14b84.10-24.14-1
5-ALL\\com\\sun\\jdi

#section:script_messages
----------messages:(5/241)----------
JDK under test: (C:/Java/jdk14b84)
java version "1.4.0-beta3"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta3-b84)
Java HotSpot(TM) Client VM (build 1.4.0-beta3-b84, mixed mode)
Timeout signalled after 120.0 seconds

#section:build
----------messages:(3/96)----------
command: build JITDebug 
reason: Named class compiled on demand
elapsed time (seconds): 1.93
result: Passed. Compilation successful

#section:compile
----------messages:(3/183)*----------
command: compile 
X:\\st1\\regression\\merlin\\jdk1.4Tests\\tests\\b84\\com\\sun\\jdi\\JITDebug.java 
reason: .class file out of date or does not exist
elapsed time (seconds): 1.93
----------System.out:(0/0)----------
----------System.err:(0/0)----------
result: Passed. Compilation successful

#section:main
----------messages:(3/115)----------
command: main JITDebug
reason: User specified action: run main/othervm JITDebug 
elapsed time (seconds): 120.01
----------System.out:(5/353)*----------
Launching: [C:\\JAVA\\JDK14B84\\JRE\\bin\\java, -Xdebug, -Xnoagent, 
-Djava.compiler=NONE, 
-Xrunjdwp:transport=dt_socket,server=y,onuncaught=y,launch=C:\\JAVA\\JDK14B84\\JRE\\bin
\\java JITDebug DEBUGGER , JITDebug, TARGET]
trigger onuncaught launch
trivial debugger started
attached to: 1040
Exception: com.sun.jdi.VMDisconnectedException - hanging
----------System.err:(0/0)----------
result: Failed. Execution failed: Program `C:/Java/jdk14b84\bin\java' interrupted! 
(timed out?)


test result: Failed. Execution failed: Program `C:/Java/jdk14b84\bin\java' interrupted! 
(timed out?)
======================================================================

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

PUBLIC COMMENTS .
10-06-2004

EVALUATION Need to address for Hopper. ###@###.### 2002-02-22 JITDebug.java is no longer a standalone regression test, due to chronic test failures on win32 platforms. When testing, use the wrapper script (JITDebug.sh) instead, which will in turn invoke JITDebug.java. The problems are related to inconsistent use of "SystemRoot" versus "SYSTEMROOT" environment variables in different win32 O/S installations. jtreg will pass SystemRoot down into the test environment, but will not pass SYSTEMROOT. Undefined SystemRoot in a win32 environment causes the low-level O/S socket() layer to fail with WSAEPROVIDERFAILEDINIT. The workaround used by JITDebug.sh and JITDebug.java is to select the dt_shmem transport on any win32 platform where SystemRoot is not found. Refer to the Comments and Evaluation on bugs 4522770 and 4461673 for more information. ###@###.### 2002-02-22
22-02-2002

SUGGESTED FIX See attached webrev file: 4522770_webrev.tar.Z ###@###.### 2002-02-22
22-02-2002