JDK-5038637 : UTF8: java -agent/-agentlib/-Xrunjdwp options not all treated as modified utf-8
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-04-27
  • Updated: 2005-01-14
  • Resolved: 2004-10-23
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.
JDK 6
6 b10Fixed
Related Reports
Relates :  
JDK-5033592 - JVMTI Doc: Inconsistent character encoding for Agent_OnLoad option string, ...
Description
The options string coming into Agent_OnLoad() are in modified UTF-8.

There are multiple strings at issue here, the transport option, and the launch option,
and the onthrow option.

See suggested fix.

This will prevent any non  ISO-Latin characters from being treated properly
when loading this agent, e.g. launch=foobar where foobar contains any
non-ISO-Latin characters will likely not work, unless the platform encoding
in indeed UTF-8 (unlikely).

###@###.### 2004-04-27
###@###.### 10/8/04 00:23 GMT
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
06-09-2004
EVALUATION Issues understood. ###@###.### 2004-06-02
02-06-2004
SUGGESTED FIX The launch option is likely the only one at issue here. The launch string is sent into the system and needs to be platform encoding. ###@###.### 2004-06-01 The transport name is also used to construct a path to a DLL/sharedLibrary , and it will need to be converetd to platform encoding. ###@###.### 2004-09-05
01-06-2004