RFR: 8333144: docker tests do not work when ubsan is configured [v4]
Thomas Stuefe
stuefe at openjdk.org
Thu Aug 1 05:53:31 UTC 2024
On Wed, 31 Jul 2024 14:07:46 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:
>> Currently when we run with ubsan - enabled binaries (configure option --enable-ubsan, see [JDK-8298448](https://bugs.openjdk.org/browse/JDK-8298448)), the docker tests do not work.
>>
>> We find this in the test output
>>
>> [STDOUT]
>> /jdk/bin/java: error while loading shared libraries: libubsan.so.1: cannot open shared object file: No such file or directory
>>
>> The container where the test is executed does not contain the ubsan package; we might skip the test in this case.
>
> Matthias Baesken has updated the pull request incrementally with two additional commits since the last revision:
>
> - remove method from WhiteBox.java
> - remove WB_isUbsanEnabled, fix test
I have seen this too late.. some questions:
- Are we sure the images the tests use will always be Debian or Debian descendants? What about RHEL or Oracle Linux?
- How close does the libubsan have to be to the compiler used to build the tested JVM? After all, UBSAN is a compiler feature. Does this work for any version of GCC used to build the JVM? Or do we risk weird test errors if libubsan in the image is incompatible with the GCC version used when building the testee JVM?
-------------
PR Comment: https://git.openjdk.org/jdk/pull/19907#issuecomment-2262093863
More information about the hotspot-dev
mailing list