| Debugging Tools for Windows |
The DEBUG_ATTACH_XXX bit-flags described in this topic control how the debugger engine attaches to a user-mode process. For the DEBUG_ATTACH_XXX options used when attaching to a kernel target, see AttachKernel.
The following table describes the possible flag values.
| Value | Description |
|---|---|
| DEBUG_ATTACH_NONINVASIVE | Attach to the target noninvasively. For more information about noninvasive debugging, see Noninvasive Debugging (User Mode). If this flag is set, then the flags DEBUG_ATTACH_EXISTING, DEBUG_ATTACH_INVASIVE_NO_INITIAL_BREAK, and DEBUG_ATTACH_INVASIVE_RESUME_PROCESS must not be set. |
| DEBUG_ATTACH_EXISTING | Re-attach to an application to which a debugger has already attached (and possibly abandoned). For more information about re-attaching to targets, see Re-attaching to the Target Application. If this flag is set, then the other DEBUG_ATTACH_XXX flags must not be set. |
| DEBUG_ATTACH_NONINVASIVE_NO_SUSPEND | Do not suspend the target's threads when attaching noninvasively. If this flag is set, then the flag DEBUG_ATTACH_NONINVASIVE must also be set. |
| DEBUG_ATTACH_INVASIVE_NO_INITIAL_BREAK | (Windows XP and later) Do not request an initial break-in when attaching to the target. If this flag is set, then the flags DEBUG_ATTACH_NONINVASIVE and DEBUG_ATTACH_EXISTING must not be set. |
| DEBUG_ATTACH_INVASIVE_RESUME_PROCESS | Resume all of the target's threads when attaching invasively. If this flag is set, then the flags DEBUG_ATTACH_NONINVASIVE and DEBUG_ATTACH_EXISTING must not be set. |
Headers: Defined in DbgEng.h. Include DbgEng.h.