RFR: 8360478: libjsig related tier3 jtreg tests fail when asan is configured [v3]
Matthias Baesken
mbaesken at openjdk.org
Thu Jul 24 13:42:58 UTC 2025
On Fri, 27 Jun 2025 07:13:26 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:
>> There are a number of :tier3 HS jtreg tests using libjsig. Unfortunately they clash with asan, so it should be avoided to run them if asan is configured.
>>
>> Examples :
>> runtime/signal/TestSigalrm.java
>> runtime/signal/TestSigbus.java
>>
>> They run into errors like this
>>
>>
>> stdout: [];
>> stderr: [==59482==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.
>>
>>
>> One option would be to avoid running those tests when asan is enabled.
>> Another option is to avoid the so called 'link order check' .
>> https://github.com/google/sanitizers/wiki/addresssanitizerflags
>>
>> verify_asan_link_order - Check position of ASan runtime in library list (needs to be disabled when other library has to be preloaded system-wide)
>
> Matthias Baesken has updated the pull request incrementally with one additional commit since the last revision:
>
> Readjust COPYRIGHT year
We could also flag the tests with ` @requires "!vm.asan"` , that would be less intrusive but needs to be done per test .
Probably in practise both approaches work, for production we do not use ASAN anyways.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/25978#issuecomment-3113525692
More information about the build-dev
mailing list