JDK-6462398 : jni spec should specify which characters are unicode-escaped when mangling
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 6
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- OS: linux
- CPU: x86
- Submitted: 2006-08-22
- Updated: 2019-07-05
- Resolved: 2015-06-02
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.
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 9 |
|---|
9Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
FULL PRODUCT VERSION : java version "1.6.0-rc" Java(TM) SE Runtime Environment (build 1.6.0-rc-b95) Java HotSpot(TM) Client VM (build 1.6.0-rc-b95, mixed mode) A DESCRIPTION OF THE PROBLEM : the jni spec (and the evaluation of bug JDK-4218179) claim that mangled names contain _0xxxx mangling for "non-ASCII Unicode characters", though experiment shows that it's obviously *much* more restrictive than that. as far as i can tell, it should say "characters other than [A-Za-z0-9]". REPRODUCIBILITY : This bug can be reproduced always.
Comments
|