JDK-4432820 : Reg-test MethodEntryExitEvents.java Failing
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 1.3.1
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2001-04-02
  • Updated: 2001-05-11
  • Resolved: 2001-04-04
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.0Resolved
Related Reports
Duplicate :  
JDK-4409241 - MethodExitEvents disappear when Object-Methods are called from main (#108885)
Description
6
    observed method exit  count: 47
----------System.err:(12/633)----------
java.lang.Exception: MethodEntryExitEvents: failed
	at MethodEntryExitEvents.runTests(MethodEntryExitEvents.java:279)
	at TestScaffold.startTests(TestScaffold.java:150)
	at MethodEntryExitEvents.main(MethodEntryExitEvents.java:113)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:484)

JavaTest Message: Test threw exception: java.lang.Exception: MethodEntryExitEvents: failed
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.Exception: MethodEntryExitEvents: failed
result: Failed. Execution failed: `main' threw exception: java.lang.Exception: MethodEntryExitEvents: failed


test result: Failed. Execution failed: `main' threw exception: java.lang.Exception: MethodEntryExitEvents: failed
======================================================================


Name: as83306			Date: 04/02/2001

Regression test com/sun/jdi/MethodEntryExitEvents.java fails with Ladybird build 20 on 
windows_2000, host qavectra 
 This test is a new test and was not available prior to build 20
 For test hardware config's, see http://sqesvr.eng/st3/jdk1.4/docs/Merlin-hw.html

#Test Results (version 2)
#Mon Mar 26 19:19:42 PST 2001
#checksum:76670ad844273d
#-----testdescription-----
$file=X:\\st1\\regression\\ladybird\\jdk1.3.1Tests\\tests\\b20\\com\\sun\\jdi\\MethodEntryExitEvents.java
$root=X:\\st1\\regression\\ladybird\\jdk1.3.1Tests\\tests\\b20
author=Tim Bell
keywords=bug4409241 othervm
library=scaffold
run=USER_SPECIFIED build JDIScaffold VMConnection\r\nUSER_SPECIFIED compile -g MethodEntryExitEvents.java\r\nUSER_SPECIFIED 
main/othervm MethodEntryExitEvents SUSPEND_ALL MethodEntryExitEventsDebugee\r\nUSER_SPECIFIED main/othervm 
MethodEntryExitEvents SUSPEND_EVENT_THREAD MethodEntryExitEventsDebugee\r\nUSER_SPECIFIED main/othervm 
MethodEntryExitEvents SUSPEND_NONE MethodEntryExitEventsDebugee\r\n
source=MethodEntryExitEvents.java
title=Test the bug fix for: MethodExitEvents disappear when Object-Methods are called from main

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

#-----testresult-----
description=file:///X:/st1/regression/ladybird/jdk1.3.1Tests/tests/b20/com/sun/jdi/MethodEntryExitEvents.java
end=Mon Mar 26 19:19:42 PST 2001
environment=regtest
execStatus=Failed. Execution failed: `main' threw exception: java.lang.Exception: MethodEntryExitEvents: failed
javatestOS=Windows 2000 5.0 (x86)
javatestVersion=JT_2.1.3i
script=com.sun.javatest.regtest.RegressionScript 
sections=script_messages build compile compile compile build main
start=Mon Mar 26 19:19:21 PST 2001
status=Failed. Execution failed: `main' threw exception: java.lang.Exception: MethodEntryExitEvents: failed
test=com/sun/jdi/MethodEntryExitEvents.java
work=C:\\Results\\Regression\\Ladybird\\b20\\QAVECTRA-Windows_NT-jth13-jdk131b20-03.26-19.10-ALL\\com\\sun\\jdi

#section:script_messages
----------messages:(1/71)----------
JDK under test: java full version "1.3.1-rc1-b20" (C:/Java/jdk131b20)

#section:build
----------messages:(3/129)----------
command: build VMConnection 
reason: User specified action: run build JDIScaffold VMConnection 
elapsed time (seconds): 5.238
result: Passed. Compilation successful

#section:compile
----------messages:(3/201)*----------
command: compile X:\\st1\\regression\\ladybird\\jdk1.3.1Tests\\tests\\b20\\com\\sun\\jdi\\scaffold\\JDIScaffold.java 
reason: .class file out of date or does not exist
elapsed time (seconds): 2.774
----------System.out:(0/0)----------
----------System.err:(0/0)----------
result: Passed. Compilation successful

#section:compile
----------messages:(3/202)*----------
command: compile X:\\st1\\regression\\ladybird\\jdk1.3.1Tests\\tests\\b20\\com\\sun\\jdi\\scaffold\\VMConnection.java 
reason: .class file out of date or does not exist
elapsed time (seconds): 2.424
----------System.out:(0/0)----------
----------System.err:(0/0)----------
result: Passed. Compilation successful

#section:compile
----------messages:(3/225)*----------
command: compile X:\\st1\\regression\\ladybird\\jdk1.3.1Tests\\tests\\b20\\com\\sun\\jdi\\MethodEntryExitEvents.java 
reason: User specified action: run compile -g MethodEntryExitEvents.java 
elapsed time (seconds): 2.514
----------System.out:(0/0)----------
----------System.err:(0/0)----------
result: Passed. Compilation successful

#section:build
----------messages:(3/109)----------
command: build MethodEntryExitEvents 
reason: Named class compiled on demand
elapsed time (seconds): 0.01
result: Passed. No need to compile: MethodEntryExitEvents.java

#section:main
----------messages:(3/221)----------
command: main MethodEntryExitEventsSUSPEND_ALL MethodEntryExitEventsDebugee
reason: User specified action: run main/othervm MethodEntryExitEvents SUSPEND_ALL MethodEntryExitEventsDebugee 
elapsed time (seconds): 13.91
----------System.out:(144/11200)----------
Suspend policy is: SUSPEND_ALL
run args: [MethodEntryExitEventsDebugee]
JVM version:1.3.1-rc1
JDI version: 1.3
JVM description: Java Debug Interface (Reference Implementation) version 1.3 
Java Debug Wire Protocol (Reference Implementation) version 1.0
JVM Debug Interface version 1.0
JVM version 1.3.1-rc1 (Java HotSpot(TM) Client VM, interpreted mode)
resumeTo loopComplete() method
Exception: instance of java.lang.ClassNotFoundException(id=4)
 at catch location: java.lang.ClassLoader.loadClass(java.lang.String, boolean)+39
stepCompleted: line#=297 event=###@###.###sLoader:297 in thread main
Exception: instance of java.util.EmptyStackException(id=8)
 at catch location: sun.misc.URLClassPath.getLoader(int)+26
stepCompleted: line#=212 event=###@###.###lassPath:212 in thread main
Exception: instance of java.util.EmptyStackException(id=8)
 at catch location: sun.misc.URLClassPath.getLoader(int)+36
stepCompleted: line#=214 event=###@###.###lassPath:214 in thread main
Exception: instance of java.lang.ClassNotFoundException(id=10)
 at catch location: java.lang.ClassLoader.loadClass(java.lang.String, boolean)+39
stepCompleted: line#=48 event=###@###.###ilegedActionException:48 in thread main
Exception: instance of java.lang.ClassNotFoundException(id=10)
 at catch location: java.lang.ClassLoader.loadClass(java.lang.String, boolean)+39
stepCompleted: line#=297 event=###@###.###sLoader:297 in thread main
 Method entry number: 1  :  ###@###.###(java.lang.String[])+0 in thread main
Exception: instance of java.lang.ClassNotFoundException(id=73)
 at catch location: java.lang.ClassLoader.loadClass(java.lang.String, boolean)+39
stepCompleted: line#=297 event=###@###.###sLoader:297 in thread main
Exception: instance of java.util.EmptyStackException(id=74)
 at catch location: sun.misc.URLClassPath.getLoader(int)+26
Exception: instance of java.util.EmptyStackException(id=74)
 at catch location: sun.misc.URLClassPath.getLoader(int)+36
stepCompleted: line#=214 event=###@###.###lassPath:214 in thread main
Exception: instance of java.lang.ClassNotFoundException(id=75)
 at catch location: java.lang.ClassLoader.loadClass(java.lang.String, boolean)+39
Exception: instance of java.lang.ClassNotFoundException(id=75)
 at catch location: java.lang.ClassLoader.loadClass(java.lang.String, boolean)+39
stepCompleted: line#=297 event=###@###.###sLoader:297 in thread main
 Method entry number: 2  :  MethodEntryEvent@t2.<init>()+0 in thread main
 Method exit  number: 1  :  MethodExitEvent@t2.<init>()+4 in thread main
 Method entry number: 3  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 4  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 5  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 6  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 7  :  ###@###.###ello5(int, int)+0 in thread main
 Method entry number: 8  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 9  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 10  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 11  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 12  :  ###@###.###ello5(int, int)+0 in thread main
 Method entry number: 13  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 14  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 15  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 16  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 17  :  ###@###.###ello5(int, int)+0 in thread main
MethodEntryExitEventsDebugee:     -->> Hello.  j is: 0 <<--
 Method exit  number: 2  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 3  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 4  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 5  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 6  :  ###@###.###ello1(int, int)+5 in thread main
 Method exit  number: 7  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 8  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 9  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 10  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 11  :  ###@###.###ello1(int, int)+5 in thread main
 Method exit  number: 12  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 13  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 14  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 15  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 16  :  ###@###.###ello1(int, int)+5 in thread main
 Method entry number: 18  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 19  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 20  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 21  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 22  :  ###@###.###ello5(int, int)+0 in thread main
 Method entry number: 23  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 24  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 25  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 26  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 27  :  ###@###.###ello5(int, int)+0 in thread main
 Method entry number: 28  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 29  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 30  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 31  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 32  :  ###@###.###ello5(int, int)+0 in thread main
MethodEntryExitEventsDebugee:     -->> Hello.  j is: 1 <<--
 Method exit  number: 17  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 18  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 19  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 20  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 21  :  ###@###.###ello1(int, int)+5 in thread main
 Method exit  number: 22  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 23  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 24  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 25  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 26  :  ###@###.###ello1(int, int)+5 in thread main
 Method exit  number: 27  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 28  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 29  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 30  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 31  :  ###@###.###ello1(int, int)+5 in thread main
 Method entry number: 33  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 34  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 35  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 36  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 37  :  ###@###.###ello5(int, int)+0 in thread main
 Method entry number: 38  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 39  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 40  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 41  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 42  :  ###@###.###ello5(int, int)+0 in thread main
 Method entry number: 43  :  ###@###.###ello1(int, int)+0 in thread main
 Method entry number: 44  :  ###@###.###ello2(int, int)+0 in thread main
 Method entry number: 45  :  ###@###.###ello3(int, int)+0 in thread main
 Method entry number: 46  :  ###@###.###ello4(int, int)+0 in thread main
 Method entry number: 47  :  ###@###.###ello5(int, int)+0 in thread main
MethodEntryExitEventsDebugee:     -->> Hello.  j is: 2 <<--
 Method exit  number: 32  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 33  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 34  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 35  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 36  :  ###@###.###ello1(int, int)+5 in thread main
 Method exit  number: 37  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 38  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 39  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 40  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 41  :  ###@###.###ello1(int, int)+5 in thread main
 Method exit  number: 42  :  ###@###.###ello5(int, int)+47 in thread main
 Method exit  number: 43  :  ###@###.###ello4(int, int)+5 in thread main
 Method exit  number: 44  :  ###@###.###ello3(int, int)+5 in thread main
 Method exit  number: 45  :  ###@###.###ello2(int, int)+5 in thread main
 Method exit  number: 46  :  ###@###.###ello1(int, int)+5 in thread main
 Method entry number: 48  :  ###@###.###Complete()+0 in thread main
MethodEntryExitEventsDebugee: executing loopComplete method for a graceful shutdown.
 Method exit  number: 47  :  ###@###.###Complete()+62 in thread main
Breakpoint at loopComplete:50 (0)
All done...

MethodEntryExitEvents: failed
    expected method entry count: 48
    observed method entry count: 48
    expected method exit  count: 4
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta2 FIXED IN: merlin-beta2 INTEGRATED IN: merlin-beta2
14-06-2004
EVALUATION This bug is a duplicate of 4409241 which was fixed in Ladybird b21. janet.koenig@Eng 2001-04-04
04-04-2001