-
Bug
-
Resolution: Fixed
-
P4
-
11, 13
-
b19
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8246628 | 11.0.9-oracle | Ralf Schmelter | P4 | Resolved | Fixed | b01 |
JDK-8231237 | 11.0.6 | Ralf Schmelter | P4 | Resolved | Fixed | b01 |
When the debugging backend listens, it sets the agent property "sun.jdwp.listenerAddress" to the current listening address.
The code currently uses NewStringUTF() to create the Java string from the C string, which assumes it is given in UTF-8. But in reality, the address is in platform encoding, so it should be converted via JNU_NewStringPlatform().
The code currently uses NewStringUTF() to create the Java string from the C string, which assumes it is given in UTF-8. But in reality, the address is in platform encoding, so it should be converted via JNU_NewStringPlatform().
- backported by
-
JDK-8231237 sun.jdwp.listenerAddress agent property uses wrong encoding
- Resolved
-
JDK-8246628 sun.jdwp.listenerAddress agent property uses wrong encoding
- Resolved
- relates to
-
JDK-8244703 "platform encoding not initialized" exceptions with debugger, JNI
- Resolved
-
JDK-8244703 "platform encoding not initialized" exceptions with debugger, JNI
- Resolved