JDK-8256864 : [windows] Improve tracing for mapping errors
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • Submitted: 2020-11-23
  • Updated: 2022-03-07
  • Resolved: 2020-12-03
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.
JDK 16
16 b28Fixed
Related Reports
Duplicate :  
JDK-8256819 - [windows] os::print_memory_mappings() should avoid probing out-of-range address areas
Relates :  
JDK-8255917 - runtime/cds/SharedBaseAddress.java failed "assert(reserved_rgn != 0LL) failed: No reserved region"
Relates :  
JDK-8280941 - os::print_memory_mappings() prints segment preceeding the inclusion range
Relates :  
JDK-8256729 - [windows] runtime/cds/SharedBaseAddress.java: assert on split_reserved_memory
Description
To analyze JDK-8256729 further, we need more tracing:

1)We should print a mapping of the split area if os::split_reserved_memory fails

2)The print-mapping code on windows has some shortcomings:
- does not handle huge areas well (it should be possible to print the whole address space, similar to proc/pid/maps on Linux)
- Protection information is printed wrong
- can be printed more concise and maybe adorned with some basic range info, e.g. library mappings
Comments
Changeset: b44a329f Author: Thomas Stuefe <stuefe@openjdk.org> Date: 2020-12-03 08:41:26 +0000 URL: https://git.openjdk.java.net/jdk/commit/b44a329f
03-12-2020