8347268: [ubsan] logOutput.cpp:357:21: runtime error: applying non-zero offset 1 to null pointer

[MBaesken]

When running ubsan-enabled binaries on macOS aarch64, the following issue is reported in the test
jdk/jfr/event/gc/detailed/TestZAllocationStallEvent.java
src/hotspot/share/logging/logOutput.cpp:357:21: runtime error: applying non-zero offset 1 to null pointer
UndefinedBehaviorSanitizer:DEADLYSIGNAL
UndefinedBehaviorSanitizer: nested bug in the same thread, aborting.

This is similar to JDK-8346881 .

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8347268: [ubsan] logOutput.cpp:357:21: runtime error: applying non-zero offset 1 to null pointer (Bug - P4)

Reviewers

• David Holmes (@dholmes-ora - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22971/head:pull/22971
$ git checkout pull/22971

Update a local copy of the PR:
$ git checkout pull/22971
$ git pull https://git.openjdk.org/jdk.git pull/22971/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22971

View PR using the GUI difftool:
$ git pr show -t 22971

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22971.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back mbaesken! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@MBaesken This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8347268: [ubsan] logOutput.cpp:357:21: runtime error: applying non-zero offset 1 to null pointer

Reviewed-by: dholmes

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 17 new commits pushed to the master branch:

• 97dd06c: 8347299: Add annotations to test cases in LicenseTest
• 0a35ebf: 8347297: Skip the RuntimeImageSymbolicLinksTest test on Windows when it is executed outside of the jtreg
• b3e8736: 8347296: WinInstallerUiTest fails in local test runs if the path to test work directory is longer that regular
• 1ade96b: 8347042: Remove an extra parenthesis in macro definition in jfrTraceIdMacros.hpp
• db7fa6a: 8347289: HKDF delayed provider selection failed with non-extractable PRK
• 0a5ef82: 8347162: Update problemlist CR for vmTestbase/nsk/jdi/VMOutOfMemoryException
• ea49537: 8310340: assert(_thread->is_interp_only_mode() || stub_caller) failed: expected a stub-caller
• 2e00816: 8346671: java/nio/file/Files/probeContentType/Basic.java fails on Windows 2025
• 88fa3b2: 8346998: Test nsk/jvmti/ResourceExhausted/resexhausted003 fails with java.lang.OutOfMemoryError when CDS is off
• 6ee2bd2: 8347147: [REDO] AccessFlags can be u2 in metadata
• ... and 7 more: https://git.openjdk.org/jdk/compare/672c413c61d9b155020a0fd4bd1c2bc0661a60fb...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@MBaesken The following label will be automatically applied to this pull request:

• hotspot-runtime

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (7823d2a0)

[dholmes-ora]

Fine and trivial.

Thanks