On Thu, 8 Aug 2024 21:05:00 GMT, Leonid Mesnik wrote:
> > FYI, this is what the (entire) debuggee output looks like for this test:
> > ```
> > Deuggee output:
> > ```
>
> Should we see the same report for CTRL+\ or after sending SIGQUIT signal? I
> see it should cause this request.
Yes, I beli
On Thu, 8 Aug 2024 20:59:24 GMT, Chris Plummer wrote:
> FYI, this is what the (entire) debuggee output looks like for this test:
>
> ```
> Deuggee output:
>
Should we see the same report for CTRL+\ or after sending SIGQUIT signal? I see
it should cause this request.
-
PR Comment:
On Thu, 8 Aug 2024 20:06:08 GMT, Chris Plummer wrote:
>> JVMTI has a somewhat unique event called DataDumpRequest. One way it is
>> triggered is via the JVMTI.data_dump jcmd, which causes JVMTI to send the
>> DataDumpRequest event to all agents that have registered for the event
>> callback. T
On Thu, 8 Aug 2024 20:06:08 GMT, Chris Plummer wrote:
>> JVMTI has a somewhat unique event called DataDumpRequest. One way it is
>> triggered is via the JVMTI.data_dump jcmd, which causes JVMTI to send the
>> DataDumpRequest event to all agents that have registered for the event
>> callback. T
On Thu, 8 Aug 2024 20:06:08 GMT, Chris Plummer wrote:
>> JVMTI has a somewhat unique event called DataDumpRequest. One way it is
>> triggered is via the JVMTI.data_dump jcmd, which causes JVMTI to send the
>> DataDumpRequest event to all agents that have registered for the event
>> callback. T
> JVMTI has a somewhat unique event called DataDumpRequest. One way it is
> triggered is via the JVMTI.data_dump jcmd, which causes JVMTI to send the
> DataDumpRequest event to all agents that have registered for the event
> callback. The agent is free to do pretty much what it wants during the
