RFR(XXS): 8007147: Trace event ExecuteVMOperation may get dangling pointer

Staffan Larsen staffan.larsen at oracle.com
Tue Feb 19 11:00:30 PST 2013

On 19 feb 2013, at 19:56, Dean Long <dean.long at oracle.com> wrote:

> When the VM_Operation is created, we could take a snapshot of the thread_id of the caller, then use that later.

One problem with that is if the thread_id gets reused for a new thread quickly after the old thread terminates. This is perhps ulikely, but could happen.

> Or we could block the creating thread from fully exiting until the VM op executes.

That would introduce a lot more synchronization and state to keep track of.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/attachments/20130219/61338d52/attachment.html 

More information about the hotspot-runtime-dev mailing list