-
Bug
-
Resolution: Fixed
-
P4
-
25
-
b05
-
aarch64
-
os_x
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8349817 | 24.0.2 | Matthias Baesken | P4 | Resolved | Fixed | b01 |
JDK-8350002 | 21.0.7 | Matthias Baesken | P4 | Resolved | Fixed | b03 |
jdk/src/hotspot/share/logging/logSelection.cpp:154:24: runtime error: applying non-zero offset 1 to null pointer
UndefinedBehaviorSanitizer:DEADLYSIGNAL
UndefinedBehaviorSanitizer: nested bug in the same thread, aborting.
(XCode 13.1 was used)
This can be seen e.g. in these jdk jtreg tests :
jdk/internal/misc/CDS/ArchivedEnumTest.java
jdk/jfr/event/gc/collection/TestGCGarbageCollectionEvent.java
jdk/jfr/startupargs/TestDumpOnExit.java
There is another issue observed here (also when running on macOS aarch64) , seems this happens in the for loop when incrementing comma_pos
" for (char *comma_pos = copy, *cur = copy; success && comma_pos != nullptr; cur = comma_pos + 1) { ..."
src/hotspot/share/logging/logSelectionList.cpp:72:94: runtime error: applying non-zero offset 1 to null pointer
UndefinedBehaviorSanitizer:DEADLYSIGNAL
UndefinedBehaviorSanitizer: nested bug in the same thread, aborting.
- backported by
-
JDK-8349817 [ubsan] logSelection.cpp:154:24 / logSelectionList.cpp:72:94 : runtime error: applying non-zero offset 1 to null pointer
-
- Resolved
-
-
JDK-8350002 [ubsan] logSelection.cpp:154:24 / logSelectionList.cpp:72:94 : runtime error: applying non-zero offset 1 to null pointer
-
- Resolved
-
- duplicates
-
JDK-8347013 [UBSAN] logSelection.cpp reported applying non-zero offset to null pointer
-
- Closed
-
- relates to
-
JDK-8347268 [ubsan] logOutput.cpp:357:21: runtime error: applying non-zero offset 1 to null pointer
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk21u-dev/7846bc63
-
Commit(master) openjdk/jdk24u/bbfe4059
-
Commit(master) openjdk/jdk/0a81676f
-
Review(master) openjdk/jdk21u-dev/1399
-
Review(master) openjdk/jdk24u/58
-
Review(master) openjdk/jdk/22903