On Thu, 20 Jul 2023 06:53:26 GMT, Serguei Spitsyn wrote:
> This problem is encountered when a JVMTI agent is loaded into running VM. The
> JvmtiExport::get_jvmti_interface() is called from the agent's Agent_OnAttach
> entrypoint. To support virtual threads it enables JVMTI notifications from
On Thu, 20 Jul 2023 06:53:26 GMT, Serguei Spitsyn wrote:
> This problem is encountered when a JVMTI agent is loaded into running VM. The
> JvmtiExport::get_jvmti_interface() is called from the agent's Agent_OnAttach
> entrypoint. To support virtual threads it enables JVMTI notifications from
On Thu, 20 Jul 2023 06:53:26 GMT, Serguei Spitsyn wrote:
> This problem is encountered when a JVMTI agent is loaded into running VM. The
> JvmtiExport::get_jvmti_interface() is called from the agent's Agent_OnAttach
> entrypoint. To support virtual threads it enables JVMTI notifications from
> This is a continuation of https://github.com/openjdk/jdk/pull/10085. I closed
> https://github.com/openjdk/jdk/pull/10085 because it had accumulated too much
> comment history and got confusing. For a history of this issue, see previous
> discussions [1] and the comment section of 10085.
>
On Tue, 18 Jul 2023 16:47:00 GMT, Sergey Nazarkin wrote:
> Hi!
>
> This is a minor HSDB fix. It prints "bad oop" instead of throwing an NPE
> message to the console when a corrupted object is found.
This pull request has now been integrated.
Changeset: a7427678
Author:Sergey Nazarkin
On Tue, 18 Jul 2023 16:47:00 GMT, Sergey Nazarkin wrote:
> Hi!
>
> This is a minor HSDB fix. It prints "bad oop" instead of throwing an NPE
> message to the console when a corrupted object is found.
Chris, Serguei, thank you for the review.
-
PR Comment:
On Fri, 14 Jul 2023 20:03:24 GMT, Thomas Stuefe wrote:
>> This is a continuation of https://github.com/openjdk/jdk/pull/10085. I
>> closed https://github.com/openjdk/jdk/pull/10085 because it had accumulated
>> too much comment history and got confusing. For a history of this issue, see
>>
On Thu, 20 Jul 2023 06:53:26 GMT, Serguei Spitsyn wrote:
> This problem is encountered when a JVMTI agent is loaded into running VM. The
> JvmtiExport::get_jvmti_interface() is called from the agent's Agent_OnAttach
> entrypoint. To support virtual threads it enables JVMTI notifications from
This problem is encountered when a JVMTI agent is loaded into running VM. The
JvmtiExport::get_jvmti_interface() is called from the agent's Agent_OnAttach
entrypoint. To support virtual threads it enables JVMTI notifications from the
VirtualThread class with a call to: