Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

DebugBreak and __debugbreak 

This topic applies to:

Visual Studio Edition

Visual Basic

C#

C++

J#

Express

No

No

Native

No

Standard

No

No

Native

No

Pro/Team

No

No

Native

No

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.

Community Additions

ADD
Show:
© 2015 Microsoft