JDK-8256819 : [windows] os::print_memory_mappings() should avoid probing out-of-range address areas
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • OS: windows
  • Submitted: 2020-11-21
  • Updated: 2021-01-07
  • Resolved: 2020-11-25
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.
Other
tbdResolved
Related Reports
Duplicate :  
JDK-8256864 - [windows] Improve tracing for mapping errors
Description
os::print_memory_mappings() - introduced with JDK-8255978 - is a handy function to list memory mappings in a given address range. In theory it can be used to print all mappings of a process. 

But it should avoid probing unnecessarily into areas which are not used, since that takes time and is pointless. On 64bit Windows, address ranges beyond 0x7ffffffffff are not mapped. If VirtualQuery does not return anything there, we should stop probing.