RFR: 8346881: [ubsan] logSelection.cpp:154:24 / logSelectionList.cpp:72:94 : runtime error: applying non-zero offset 1 to null pointer [v2]

[Matthias Baesken]

On Thu, 2 Jan 2025 14:29:10 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:

>> When running jtreg tests on macOS aarch64 with ubsanized binaries, the following error is reported :
>> 
>> 
>> 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.
>
> Matthias Baesken has updated the pull request incrementally with one additional commit since the last revision:
> 
>   for loop check has been moved

Seems we have a similar one here,  show by test runtime/MemberName/MemberNameLeak  (macOS aarch64) 

`src/hotspot/share/logging/logDecorators.cpp:103:23: runtime error: applying non-zero offset 1 to null pointer`

Should I address it here too ?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/22903#issuecomment-2567976367