Currently RelocIterator assumes that address of relocation data is never null even when there were no relocations. It never checks for null and assumes that `current - 1` address is valid.
It was true beforeJDK-8343789 which moved relocation data from code blob.
JDK-8352112 resolved the issue with setting relocation data address to some valid address.
We should consider enabling RelocIterator correctly handle null address of relocation data.
It was true before
We should consider enabling RelocIterator correctly handle null address of relocation data.
- relates to
-
JDK-8352112 [ubsan] hotspot/share/code/relocInfo.cpp:130:37: runtime error: applying non-zero offset 18446744073709551614 to null pointer
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/0bfa636c
-
Review(master)
openjdk/jdk/24203