RFR(XXS): 8007147: Trace event ExecuteVMOperation may get dangling pointer (original) (raw)
Staffan Larsen staffan.larsen at oracle.com
Tue Feb 19 11:00:30 PST 2013
- Previous message: RFR(XXS): 8007147: Trace event ExecuteVMOperation may get dangling pointer
- Next message: RFR(XXS): 8007147: Trace event ExecuteVMOperation may get dangling pointer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 19 feb 2013, at 19:56, Dean Long <dean.long at oracle.com> wrote:
When the VMOperation is created, we could take a snapshot of the threadid 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.
/Staffan
-------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20130219/61338d52/attachment-0001.html
- Previous message: RFR(XXS): 8007147: Trace event ExecuteVMOperation may get dangling pointer
- Next message: RFR(XXS): 8007147: Trace event ExecuteVMOperation may get dangling pointer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]