Back in 2022 Zhengyu Gu had the very nice idea of using NMT mapping info for smartening up pp in gdb: JDK-8280289.
The same idea could be applied to hs_err file location printing. NMT has information about all its mappings and can tell us where it thinks a given unknown pointer points into.
This could be even more useful if the "find malloc block" part of that functionality would be smarter. As it is now, it only works if the pointer in question points to the start of a user-allocated area. Would be nice if the code could (carefully) search for the next valid-looking malloc header instead.
The same idea could be applied to hs_err file location printing. NMT has information about all its mappings and can tell us where it thinks a given unknown pointer points into.
This could be even more useful if the "find malloc block" part of that functionality would be smarter. As it is now, it only works if the pointer in question points to the start of a user-allocated area. Would be nice if the code could (carefully) search for the next valid-looking malloc header instead.
- relates to
-
JDK-8305414 gtest/NMTGtests.java is failing various sub-tests
-
- Closed
-
-
JDK-8306454 gtest/GTestWrapper.java fails two NMT.location_printing_cheap_dead tests
-
- Closed
-
-
JDK-8306462 Remove NMT gtests that test dead-block-printing
-
- Closed
-
-
JDK-8280289 Enhance debug pp() command with NMT info
-
- Resolved
-
(1 links to)