-
Bug
-
Resolution: Fixed
-
P3
-
1.4.0
-
beta
-
x86
-
windows_nt
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2032444 | 1.4.0 | Karen Kinnear | P3 | Closed | Fixed | beta |
Name: dkC59003 Date: 03/03/2000
Hotspot VM build 1.4merlin-internal-debug for win32 fails the test
nsk/jvmpi/GetCallTrace/calltr001
from the testbase_nsk with the assertion failure: "wrong call"
This is observed when METHOD_ENTRY event is enabled in the JVM_OnLoad
function.
To reproduce the bug run
doit.bat <jdk root directory>
in
/net/sqesvr/vsn/GammaBase/Bugs/<this bug number>
When running on winNT the test outputs:
>doit G:\ld24\java\hotspot\jdk1.3.0pi
...
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-U)
Java HotSpot(TM) Client VM (build 1.4merlin-internal-debug, mixed mode)
#
#
# HotSpot Virtual Machine Error, assertion failure
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# assert(jvmpi::is_event_enabled(((jint) 3)), "wrong call")
#
# Error ID: L:\ws\hotspot\main\baseline-dev\src\cpu\i486\vm\c1_CodeEmitter_i486.cpp, 2523
#
# Problematic Thread: prio=5 tid=0x7818a8 nid=0x19f runnable
#
======================================================================
karen.kinnear@East 2000-05-31
This problem also occurs on Solaris/Intel when enabling METHOD_ENTRY events,
when run with C1 debug.
See test for 4329161 as well.
- backported by
-
JDK-2032444 METHOD_ENTRY event enabled in JVM_OnLoad causes assertion failure
-
- Closed
-