Fix missing unsafe available check

[laurit]

Resolves #6913

[trask]

is it worth (possible?) adding something in CI that runs the tests without unsafe?

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.09%. Comparing base (d2a0299) to head (2a01ce7).
Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
...emetry/exporter/internal/marshal/UnsafeString.java	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #6920      +/-   ##
============================================
- Coverage     90.10%   90.09%   -0.02%     
  Complexity     6594     6594              
============================================
  Files           729      729              
  Lines         19828    19828              
  Branches       1950     1951       +1     
============================================
- Hits          17867    17865       -2     
  Misses         1369     1369              
- Partials        592      594       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[laurit]

is it worth (possible?) adding something in CI that runs the tests without unsafe?

added a test that uses a custom class loader to hide sun.misc.Unsafe from the tested code

[jack-berg]

Thanks for the fix!

[io7m]

Can confirm this fixes the issue. 👍

[trask]

is it worth (possible?) adding something in CI that runs the tests without unsafe?

added a test that uses a custom class loader to hide sun.misc.Unsafe from the tested code

ah I see the problem with using something like --sun-misc-unsafe-memory-access=deny is that then gradle/kotlin itself fails 😢

Caused by: java.lang.UnsupportedOperationException: objectFieldOffset
at org.jetbrains.kotlin.com.intellij.util.containers.Unsafe.objectFieldOffset(Unsafe.java:126)