-
Bug
-
Resolution: Fixed
-
P5
-
1.3.0, 1.4.2, 5.0
-
tiger
-
generic
-
generic
-
Verified
Name: dkC59003 Date: 12/17/99
JVMDI spec "Get Local Variable" section reads:
"The functions return one of the following error codes:
....
JVMDI_ERROR_TYPE_MISMATCH
The variable is not an appropriate type for the function used."
The HotSpot VM 1.3fcs-R (both win32 and Solaris) fails the test
nsk/jvmdi/GetLocalVariable/getlocal002 from testbase_nsk as GetLocalInt and
GetLocalDouble functions do not see a mismatch between the type of a local
variable and their own type.
Classic also fails the test.
To reproduce the bug run
doit.sh <jdk root directory>
in
GammaBase/Bugs/<this bug number>
The test outputs:
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-Q)
Java HotSpot(TM) Client VM (build 1.3-R, interpreted mode)
Failed to return JVMDI_ERROR_TYPE_MISMATCH. err = 0
intVal = 1086324736
Failed to return JVMDI_ERROR_TYPE_MISMATCH for double. err = 0
======================================================================
Name: elR10090 Date: 01/20/2002
The same is true for "Set Local Variable" functions set.
This bug also affects the following test from testbase_nsk:
nsk/jvmdi/SetLocalVariable/setlocal004
Pavel Vysotski <###@###.###>
======================================================================
Name: ipR10196 Date: 08/26/2003
Similar bug is revealed for the corresponding JVMTI functions
GetLocal*/SetLocal*. The tests affected are:
nsk/jvmti/GetLocalVariable/getlocal002
nsk/jvmti/SetLocalVariable/setlocal004
Ivan Popov <###@###.###>
======================================================================
- relates to
-
JDK-4958038 JVMTI spec: INVALID_SLOT/TYPE_MISMATCH errors should be optional
-
- Closed
-
-
JDK-4921631 SIGBUS in Get/SetLocalLong and Get/SetLocalDouble functions
-
- Closed
-
-
JDK-4312617 JVMDI: GetLocal* functions do not track TYPE_MISMATCH error
-
- Closed
-
-
JDK-8080406 VM_GetOrSetLocal doesn't check local slot type against requested type
-
- Resolved
-