RFR: 8357826: Avoid running some jtreg tests when asan is configured [v2]

Matthias Baesken mbaesken at openjdk.org
Wed Jun 4 14:17:52 UTC 2025


On Mon, 2 Jun 2025 08:07:38 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:

>> There are a couple of jtreg tests, especially in the HS area, with very special assumptions about memory layout/sizes .
>> Those fail when the address sanitizer is configured ( --enable-asan ).
>> The change adds a way to tag those tests with 'requires' so that they can be avoided easily when running jtreg tests with ASAN enabled.
>> Adjusting the tests for "pleasing" the sanitizer is not always desired (if possible for some tests it can be done later) .
>> While at it, also same is also added for ubsan .
>
> Matthias Baesken has updated the pull request incrementally with one additional commit since the last revision:
> 
>   TestBreakSignalThreadDump has issues with asan

Had a look at HS tier3 tests too and the whole runtime/signal/TestSig*  tests fail with asan like this
e.g. runtime/signal/TestSigalrm.java

 stdout: [];
 stderr: [==3863397==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD.


So maybe we should mark them too ?
Seems to be the same kind of issue as in the HS tier1 jsig  related tests.

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

PR Comment: https://git.openjdk.org/jdk/pull/25575#issuecomment-2940211436


More information about the serviceability-dev mailing list