Re: JDWP thread suspending user java threads
On 29-06-2010 22:33, Mike Schilling wrote:
"Arne Vajh?j" <arne@vajhoej.dk> wrote in message
news:4c2aab72$0$281$14726298@news.sunsite.dk...
On 29-06-2010 21:45, Ethan wrote:
I came to know that JDWP thread is used for debugging and that it is
used by the debugger to suspend other user java threads. In a previous
post, it seems like most modern JVMs leave thread management to their
native OS, hence it wouldn't be possible for JDWP to directly suspend
other user java threads and it could at the best hope to have them
finish their work and move out of ready queue.
If this is the case, how would it work with a java thread that is in
an infinite loop, good enough to ensure that it doesn't finish at all?
If not please share any links as to how it works.
If the native thread API allows for suspension then the JVM
can use that.
Otherwise I guess that it would need to get something
put in the code running in the thread.
The JVM is (mostly) an interpreter; that gives it control over all the
threads.
I would have expected it to be JIT compiled.
But I think you are correct - when executing under the debugger
it will probably interpret.
Arne