On Wed, 3 Apr 2024 07:02:31 GMT, Tomáš Zezula wrote:
> Problem:
> The debugging stack traces in `jdk.internal.vm.TranslatedException` do not
> work in libjvmci because they are enabled via the
> `jdk.internal.vm.TranslatedException.debug` system property. However, HotSpot
> sy
tProperty()` in libjvmci.
>
> Fix:
> The value of `jdk.internal.vm.TranslatedException.debug` is passed from the
> VM via a boolean flag to `VMSupport::decodeAndThrowThrowable()`.
Tomáš Zezula has updated the pull request incrementally with one additional
commit since the last revi
tProperty()` in libjvmci.
>
> Fix:
> The value of `jdk.internal.vm.TranslatedException.debug` is passed from the
> VM via a boolean flag to `VMSupport::decodeAndThrowThrowable()`.
Tomáš Zezula has updated the pull request incrementally with one additional
commit since the last revi
Problem:
The debugging stack traces in the `jdk.internal.vm.TranslatedException` do not
work in the libjvmci compiler becuase they are enabled using the system
property `jdk.internal.vm.TranslatedException.debug`. However, the libjvmci
compiler does not copy HotSpot VM system properties. Instead