On 02/06/2018 06:36, David Holmes wrote:
On 2/06/2018 10:43 AM, Stuart Marks wrote:
:
It looks to me like this interface resides on the debugger side of
JDWP. I don't know exactly where it's implemented in the target VM,
but I imagine it goes through some VM-internal or JDWP implementation
interface, not through the target VM's public
java.lang.Thread.stop(thr) interface. Is that right? (I'm not that
familiar with this area of the system.)
It's a rather complex setup but the backend that does the work is
(usually?) JVM TI, which won't go back out through the Java API.
Right, there's a StopThread function in JVM TI and a corresponding Stop
Command in the JDWP protocol. The JVM TI spec has a statement to say
that it works "similar to Thread.stop" and the JDWP spec has "as if done
by Thread.stop" so it would be good to update both of these.
-Alan
