On Tue, 13 Aug 2024 22:28:10 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.
On Tue, 13 Aug 2024 22:28:10 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.
On Tue, 13 Aug 2024 21:18:04 GMT, Serguei Spitsyn wrote:
>> Chris Plummer has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> git rid of unnecessary @build
>
> Looks good.
@sspitsyn or @lmesnik I need a final review since I made a minor cod
On Tue, 13 Aug 2024 22:28:10 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.
> 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
On Mon, 12 Aug 2024 21:35:49 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.
On Mon, 12 Aug 2024 21:35:49 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.
On Mon, 12 Aug 2024 19:22:13 GMT, Leonid Mesnik wrote:
>> It's not needed because it is in the same file. I'm not even sure it would
>> work.
>
> ough, I mean 'is @build DataDumpTest' needed to build DataDumpTestTarg? The
> DataDumpTest should be built without explicit @build command.
Ok. I re
> 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
On Thu, 8 Aug 2024 20:56:16 GMT, Chris Plummer wrote:
>> test/jdk/com/sun/jdi/DataDumpTest.java line 51:
>>
>>> 49: * @library /test/lib
>>> 50: * @modules jdk.jdi
>>> 51: * @build DataDumpTest
>>
>> Is the build needed to build 'DataDumpTestTarg' because it is not explicitly
>> used by the
On Wed, 31 Jul 2024 10:12:16 GMT, Serguei Spitsyn wrote:
>> Chris Plummer has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Get rid of timeout. Use driver instead of othervm
>
> First, it is a good idea to implement/enable this.
> It looks
> 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
On Thu, 8 Aug 2024 19:59:04 GMT, Leonid Mesnik wrote:
>> Chris Plummer has updated the pull request incrementally with two additional
>> commits since the last revision:
>>
>> - Minor improvment to datadump output
>> - Add test cast for new debug agent datadump support
>
> test/jdk/com/sun/jd
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 19:28:09 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
> 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
On Wed, 31 Jul 2024 10:12:16 GMT, Serguei Spitsyn wrote:
> Did you consider to add a test for this?
Good idea. I'll add one.
-
PR Comment: https://git.openjdk.org/jdk/pull/20367#issuecomment-2260951141
On Sat, 27 Jul 2024 02:12:33 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. The
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
callbac
24 matches
Mail list logo
