|
From: | Bryce McKinlay |
Subject: | Re: [cp-patches] [RFA/JDWP] ClassTypeCommandSet |
Date: | Thu, 04 Aug 2005 18:22:08 -0400 |
User-agent: | Mozilla Thunderbird 1.0 (X11/20041206) |
Aaron Luchko wrote:
+ try + {+ if ((invokeOpts & JdwpConstants.InvokeOptions.INVOKE_SINGLE_THREADED) + != 0)+ { + // We must suspend all running threads first + suspendSuccess = vm.suspendAllThreadsExcept(Thread.currentThread(). + getThreadGroup()); + } + return vm.executeMethod(null, thread, clazz, method, values, + false); + } + catch (Exception ex) + { + if (suspendSuccess) + { // We must first resume the suspended threads + vm.resumeAllThreadsExcept(Thread.currentThread().getThreadGroup()); + }
What happens if some threads are already suspended by the debugger? Looks like this would resume them which wouldn't be the expected behaviour.
Bryce
[Prev in Thread] | Current Thread | [Next in Thread] |