When generating a stack trace with the hotspot VM , (I tried merlin)
you cannot see which VM generated the stack trace. This information
is available with classic VM and is very useful for debugging customer
stack traces, especially when the VM in embedded in something like
the plugin where the customer doesn't even know what VM they think is
running
I'm logging this as a fix for 1.4, as there is no classic VM in 1.4 and
so it could be looked as a regression
Should be very simple to implement
classic:
Full thread dump Classic VM (1.3.1-rc2-b23, green threads):
"Thread-249" (TID:0x40f1ebe8, sys_thread_t:0x83e3de8, state:CW) prio=5
Hotspot:
"Thread-0" prio=1 tid=0x0x58409bb0 nid=0xb39 waiting on monitor [0..bfffd818]
you cannot see which VM generated the stack trace. This information
is available with classic VM and is very useful for debugging customer
stack traces, especially when the VM in embedded in something like
the plugin where the customer doesn't even know what VM they think is
running
I'm logging this as a fix for 1.4, as there is no classic VM in 1.4 and
so it could be looked as a regression
Should be very simple to implement
classic:
Full thread dump Classic VM (1.3.1-rc2-b23, green threads):
"Thread-249" (TID:0x40f1ebe8, sys_thread_t:0x83e3de8, state:CW) prio=5
Hotspot:
"Thread-0" prio=1 tid=0x0x58409bb0 nid=0xb39 waiting on monitor [0..bfffd818]