Lines Matching full:debugger
126 * debugger. Create the JDWP thread and let it continue the mission.
147 * For suspend=y, wait for the debugger to connect to us or for us to
148 * connect to the debugger.
168 * Ordinarily we would pause briefly to allow the debugger to set
184 * a debugger attached.
186 * This includes freeing up the debugger event list.
196 * Should not have one of these in progress. If the debugger went away
245 * Are we talking to a debugger?
279 * non-server mode, we bail out of the thread when the debugger drops
282 * We broadcast a notification when a debugger attaches, after we
298 * debugger. To support the "timeout=xxx" option we need to
314 /* process requests until the debugger drops */
355 /* tell the interpreter that the debugger is no longer around */
375 * Return the thread handle, or (pthread_t)0 if the debugger isn't running.
390 * instant the debugger connects, because we run the risk of executing code
391 * before the debugger has had a chance to configure breakpoints or issue
395 * There's no JDWP event we can post to tell the debugger, "we've stopped,
397 * cause the debugger to immediately send a resume, but the debugger might
401 * What we really want is a "wait until the debugger is done configuring
402 * stuff" event. We can approximate this with a "wait until the debugger
423 * Return the time, in milliseconds, since the last debugger activity.
425 * Returns -1 if no debugger is attached, or 0 if we're in the middle of
426 * processing a debugger request.
431 ALOGD("dvmJdwpLastDebuggerActivity: no active debugger");
447 ALOGV("+++ debugger interval=%lld", now - last);
