JDK-4698210 : GetCapabilities() interface does not zero out unused bits
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmdi
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-06-06
  • Updated: 2002-11-26
  • Resolved: 2002-08-27
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.2 mantisFixed
Related Reports
Relates :  
Relates :  
Description
###@###.### 2002-06-06

The HotSpot implementation of JVM/DI GetCapabilities() does not
zero out the unused bits. This means that newer versions of the
JPDA backend will see random results when querying capabilities
of older HotSpot VMs.

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

SUGGESTED FIX ###@###.### 2002-06-06 The JVMDI_capabilities object needs to be zeroed out before HotSpot defines the capabilities that it supports. ###@###.### 2002-06-07 Here is the context diff for the change: ------- src/share/vm/prims/jvmdi_info.cpp ------- *** /tmp/sccs.6laiNW Fri Jun 7 10:22:43 2002 --- jvmdi_info.cpp Thu Jun 6 12:11:40 2002 *************** *** 934,939 **** --- 934,941 ---- NULL_CHECK(capabilitiesPtr, JVMDI_ERROR_NULL_POINTER); { JVMDI_capabilities result; + memset(&result, 0, sizeof(result)); // unused values need to be false + result.can_watch_field_modification = JNI_TRUE; result.can_watch_field_access = JNI_TRUE; result.can_get_bytecodes = JNI_TRUE;
11-06-2004

PUBLIC COMMENTS .
10-06-2004

EVALUATION ###@###.### 2002-06-07 The fix for the following bug: 4478469 4/2 single stepping with lots of Java threads is very slow adds a new capability field to JVM/DI. This bug is exposed by this addition.
07-06-2002