JDK-8237250 : pmap and pstack should do a better of making it clear that they are not supported on Mac OS X
- Type: Bug
- Component: hotspot
- Sub-Component: svc-agent
- Affected Version: 15
- Priority: P5
- Status: Resolved
- Resolution: Fixed
- OS: os_x
- Submitted: 2020-01-15
- Updated: 2020-04-16
- Resolved: 2020-04-13
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 15 |
|---|
15 b19Fixed  |
Related Reports
|
Relates :
|
Description
pmap and pstack are not supported on Mac OS X. pstack will give the message "Not available on Darwin". Although the darwin kernel might be the technical reason why it doesn't work, it would be better to the end user to clarify that it is not supported on "Mac OS X" rather than Darwin. pmap simply produces no output, not even an error message. I looked into this a bit. We are getting into PMap.run(), but it appears the call to CDebugger.getLoadObjectList() is returning an empty list, so nothing is output. We should add an extra check and println here that calls out that pmap is not supported on Mac OS X. The ClhsdbPMap and ClhsdbPStack tests should also be fixed to attempt to run on Mac OS X and check for the appropriate error messages. Right now they are excluded from running on Mac OS X. The reason I initially started looking into the Mac OS X support for these two tools is because these two tests were excluded on OSX, and I was curious as to why so I experimented with enabling them to see the result.
Comments
|