Hello,
if a Java agent fails to retransform due to a verification error (using
Instrumentation.retransformClasses), this error does not contain a message.
This is like it used to be for all verification errors, when a class was
loaded for the first time, but this feature of displaying a message an
On Fri, 16 Apr 2021 20:30:15 GMT, Rafael Winterhalter
wrote:
>> To allow agents the definition of auxiliary classes, an API is needed to
>> allow this. Currently, this is often achieved by using `sun.misc.Unsafe` or
>> `jdk.internal.misc.Unsafe` ever since the `defineClass`
On Thu, 25 Jan 2024 10:04:08 GMT, Andrew Dinn wrote:
> pass a non-null Instrumentation instance i.e. to have agent capabilities.
What stops people from supplying a fake instance? Wouldn't you need to "test
run" the instance first?
-
PR Comment: https://git.openjdk.org/jdk/pull/354
On Fri, 16 Apr 2021 20:30:15 GMT, Rafael Winterhalter
wrote:
>> To allow agents the definition of auxiliary classes, an API is needed to
>> allow this. Currently, this is often achieved by using `sun.misc.Unsafe` or
>> `jdk.internal.misc.Unsafe` ever since the `defineClass`
On Fri, 16 Apr 2021 20:30:15 GMT, Rafael Winterhalter
wrote:
>> To allow agents the definition of auxiliary classes, an API is needed to
>> allow this. Currently, this is often achieved by using `sun.misc.Unsafe` or
>> `jdk.internal.misc.Unsafe` ever since the `defineClass`
On Fri, 16 Apr 2021 20:30:15 GMT, Rafael Winterhalter
wrote:
>> To allow agents the definition of auxiliary classes, an API is needed to
>> allow this. Currently, this is often achieved by using `sun.misc.Unsafe` or
>> `jdk.internal.misc.Unsafe` ever since the `defineClass`
