DebugBreak and __debugbreak
The document is archived and information here might be outdated

DebugBreak and __debugbreak

This topic applies to:

Edition

Visual Basic

C#

C++

Web Developer

Express

Topic does not applyTopic does not apply

Native only

Topic does not apply

Standard

Topic does not applyTopic does not apply

Native only

Topic does not apply

Pro and Team

Topic does not applyTopic does not apply

Native only

Topic does not apply

Table legend:

Topic applies

Applies

Topic does not apply

Does not apply

Topic applies but command hidden by default

Command or commands hidden by default.

You can call the DebugBreak Win32 function or the __debugbreak intrinsic at any point in your code. DebugBreak and __debugbreak have the same effect as setting a breakpoint at that location.

Because DebugBreak is a call to a system function, system debug symbols must be installed to ensure the correct call stack information is displayed after breaking. Otherwise, the call stack information displayed by the debugger may be off by one frame. If you use __debugbreak, symbols are not required.

Show:
© 2016 Microsoft