Lines Matching full:debugger
67 All threads are native pthreads. All threads, except the JDWP debugger
68 thread, are visible to code running in the VM and to the debugger. (We
69 don't want the debugger to try to manipulate the thread that listens for
70 instructions from the debugger.) Internal VM threads are in the "system"
77 Certain debugger events may inspire threads to self-suspend.
88 Threads may be suspended by the GC, debugger, or the SIGQUIT listener
89 thread. The debugger may suspend or resume individual threads, while the
93 a debugger requirement: if the debugger suspends a thread, the thread is
94 not allowed to run again until the debugger resumes it (or disconnects,
95 in which case we must resume all debugger-suspended threads).
118 The debugger may choose to suspend or resume a single thread, which can
120 will only check for suspension of single threads when the debugger is
126 debugger attached.)
128 The debugger is not allowed to resume threads suspended by the GC. This
129 is trivially enforced by ignoring debugger requests while the GC is running
137 though at present the only performance impact is on the debugger (see
159 holding the thread list lock, it will prevent the GC or debugger from
172 debugger threads. The mutexes guarding those go into the "critical
180 resources in the GC or debugger (#1) or waiting for threads to suspend
186 safe-pointing. Because the GC and debugger are fairly intrusive, there
441 * GC and the debugger from simultaneously suspending all threads.
473 * Could be the debugger telling us to resume at roughly
1345 * We have to deal with an odd race with the GC/debugger suspension
1398 * suspend singly by the debugger, the child should not inherit the value.
1512 * Notify the debugger & DDM. The debugger notification may cause
1808 * the debugger something to show. It is essential for the JNI-attached
1948 /* tell the debugger & DDM */
2074 * Tell the debugger & DDM. This may cause the current thread or all
2176 * This is used primarily for debugger/DDMS activity. Does not return
2204 * Used primarily for debugger/DDMS activity. The thread in question
2236 * Suspend yourself, as a result of debugger activity.
2242 /* debugger thread must not suspend itself due to debugger activity! */
2283 * can happen if the debugger lets go while a SIGQUIT thread
2419 * part of a debugger action in which the JDWP thread is always the one
2523 * the debugger, and by any thread that hits a "suspend all threads"
2524 * debugger event (e.g. breakpoint or exception).
2527 * to suspend the JDWP thread. For the GC, we do, because the debugger can
2532 * various debugger gymnastics, so keeping an "everybody is suspended" flag
2565 * of interest to the debugger.
2579 /* debugger events don't suspend JDWP thread */
2602 * self-suspending for the debugger) it won't block while we're waiting
2609 /* debugger events don't suspend JDWP thread */
2652 /* debugger events don't suspend JDWP thread */
2725 * Undo any debugger suspensions. This is called when the debugger
2747 /* debugger events don't suspend JDWP thread */
2786 * intended for use by the debugger.
2810 * to suspend itself after sending an event to the debugger.
2819 * debugger event, that's not really a possibility. (To avoid deadlock,
3559 /* suppress the heapworker watchdog to assist anyone using a debugger */
