JDK-5049313 : Implement all JVMTI strings as modified UTF-8
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2004-05-18
  • Updated: 2023-12-13
  • Resolved: 2016-11-03
Related Reports
Relates :  
JDK-5033592 - JVMTI Doc: Inconsistent character encoding for Agent_OnLoad option string, ...
Relates :  
JDK-4915107 - Clarify supplementary character handling in modified UTF-8
Relates :  
JDK-5044673 - JVMTI Doc: Clarify supplementary character handling is modified UTF-8
Description
Bug 5044673 (the JVMTI portion of 4915107) is to clarify that JVMTI character
strings are modified UTF-8.  Parameters to the Agent_OnLoad entry point and
the four functions GetSystemProperty, SetSystemProperty, GetSystemProperties, 
and AddToBootstrapClassLoaderSearch were not included since they could not be
implemented as UTF-8 in Tiger.  The decision has been made to specify these 
as modified UTF-8 (bug 5033592).  This bug tracks that the implementation of
these five does not match the specification.
Comments
This is not on our list of current priorities, if this changes please re-open this issue.
03-11-2016
SUGGESTED FIX These five must be converted to modified UTF-8.
11-06-2004
PUBLIC COMMENTS All JVMTI strings, including the parameters to the Agent_OnLoad entry point and the four functions GetSystemProperty, SetSystemProperty, GetSystemProperties, and AddToBootstrapClassLoaderSearch, are encoded as modified UTF-8.
10-06-2004
EVALUATION See Description and Suggested Fix ###@###.### 2004-05-18
18-05-2004