Share via

DEBUG_REASON

  • Article

Applies to: yesVisual Studio noVisual Studio for Mac

Note

This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

Specifies why the process was launched for debugging.

Syntax

enum enum_DEBUG_REASON {
    DEBUG_REASON_ERROR         = 0,
    DEBUG_REASON_USER_LAUNCHED = 1,
    DEBUG_REASON_USER_ATTACHED = 2,
    DEBUG_REASON_AUTO_ATTACHED = 3,
    DEBUG_REASON_CAUSALITY     = 4
};
typedef DWORD DEBUG_REASON;

public enum enum_DEBUG_REASON {
    DEBUG_REASON_ERROR         = 0,
    DEBUG_REASON_USER_LAUNCHED = 1,
    DEBUG_REASON_USER_ATTACHED = 2,
    DEBUG_REASON_AUTO_ATTACHED = 3,
    DEBUG_REASON_CAUSALITY     = 4
};

Fields

DEBUG_REASON_ERROR
A non-specific error occurred (this is used as a default condition when none of the other reasons fit).

DEBUG_REASON_USER_LAUNCHED
The process was launched at the user's request.

DEBUG_REASON_USER_ATTACHED
The already-running process was attached to by the user.

DEBUG_REASON_AUTO_ATTACHED
The process was automatically attached to when it was launched.

DEBUG_REASON_CAUSALITY
The process was launched due to a Just-In-Time (JIT) debugging event.

Remarks

Returned from the GetDebugReason method.

Requirements

Header: msdbg.h

Namespace: Microsoft.VisualStudio.Debugger.Interop

Assembly: Microsoft.VisualStudio.Debugger.Interop.dll

See also