JDK-7185672 : jstack, jinfo, etc. fail even after signing on 10.8
- Type: Bug
- Component: core-svc
- Sub-Component: tools
- Affected Version: 7u6
- Priority: P2
- Status: Closed
- Resolution: Cannot Reproduce
- OS: os_x
- CPU: x86
- Submitted: 2012-07-20
- Updated: 2017-02-11
- Resolved: 2012-09-10
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 7 |
|---|
7u40Resolved  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
For 7u6 we agreed that it was not necessary to sign the binaries for jinfo, jstack, and the other serviceability tools. This means that the -F option won't work because they require the ability to access the internals of another process. While investigating code signing I found that just about anything that can be trusted back to a root CA will work, so I signed jstack with our Developer ID certificate. Once I did that the tool gets farther but still fails with the attached log. I'm no expert on these tools, but there's no useful information in the output. We've already decided to defer a fix this needs to 7u8, so we should defer this one too. Ok dev / nloodin ok SQE / ctornqvi This might also have to be release noted? added the release-note=yes keyword to flag this issue for inclusion in the release note
Comments
|