Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang [v2]

2025-06-30 Thread Matthias Baesken
On Mon, 30 Jun 2025 07:02:31 GMT, Matthias Baesken wrote: >> A couple of tests e.g. VendorInfoPluginsTest but also some Hotspot like >> runtime/ErrorHandling/CreateCoredumpOnCrash.java put (write) to special >> addresses like 0 to provoke crashs. >> However this does not work well with ubsan-en

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang [v2]

2025-06-30 Thread Matthias Baesken
> A couple of tests e.g. VendorInfoPluginsTest but also some Hotspot like > runtime/ErrorHandling/CreateCoredumpOnCrash.java put (write) to special > addresses like 0 to provoke crashs. > However this does not work well with ubsan-enabled binaries on the clang > based platforms (macOS, AIX). > T

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-28 Thread Matthias Baesken
On Sat, 28 Jun 2025 03:55:44 GMT, Kim Barrett wrote: > Does the same problem arise when building with clang on linux? I tried it, > but ran into some linking errors that I don't understand, and I've not done > much with ubsan before. > > ``` > ld.lld: error: non-exported symbol '__ubsan_handle

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-27 Thread Kim Barrett
On Fri, 27 Jun 2025 21:13:32 GMT, Magnus Ihse Bursie wrote: >>> I agree, this does not seem to be limited to clang, unless the signal >>> handling stuff differs in ubsan in different compilers. >> >> I only see issues with clang (on macOS and AIX) ; the Linux platforms using >> gcc are fine.

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-27 Thread Magnus Ihse Bursie
On Fri, 27 Jun 2025 19:11:28 GMT, Matthias Baesken wrote: >> I agree, this does not seem to be limited to clang, unless the signal >> handling stuff differs in ubsan in different compilers. > >> I agree, this does not seem to be limited to clang, unless the signal >> handling stuff differs in u

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-27 Thread Matthias Baesken
On Fri, 27 Jun 2025 09:30:19 GMT, Matthias Baesken wrote: > A couple of tests e.g. VendorInfoPluginsTest but also some Hotspot like > runtime/ErrorHandling/CreateCoredumpOnCrash.java put (write) to special > addresses like 0 to provoke crashs. > However this does not work well with ubsan-enable

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-27 Thread Matthias Baesken
On Fri, 27 Jun 2025 15:56:32 GMT, Magnus Ihse Bursie wrote: > I agree, this does not seem to be limited to clang, unless the signal > handling stuff differs in ubsan in different compilers. I only see issues with clang (on macOS and AIX) ; the Linux platforms using gcc are fine.

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-27 Thread Magnus Ihse Bursie
On Fri, 27 Jun 2025 15:45:22 GMT, Kim Barrett wrote: >> A couple of tests e.g. VendorInfoPluginsTest but also some Hotspot like >> runtime/ErrorHandling/CreateCoredumpOnCrash.java put (write) to special >> addresses like 0 to provoke crashs. >> However this does not work well with ubsan-enabled

Re: RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-27 Thread Kim Barrett
On Fri, 27 Jun 2025 09:30:19 GMT, Matthias Baesken wrote: > A couple of tests e.g. VendorInfoPluginsTest but also some Hotspot like > runtime/ErrorHandling/CreateCoredumpOnCrash.java put (write) to special > addresses like 0 to provoke crashs. > However this does not work well with ubsan-enable

RFR: 8360791: [ubsan] Adjust signal handling when using clang

2025-06-27 Thread Matthias Baesken
A couple of tests e.g. VendorInfoPluginsTest but also some Hotspot like runtime/ErrorHandling/CreateCoredumpOnCrash.java put (write) to special addresses like 0 to provoke crashs. However this does not work well with ubsan-enabled binaries on the clang based platforms (macOS, AIX). The mentioned