Breakpoint Macros and Function

You can use the breakpoint macros and function to break into the debugger (either the regular debugger or the kernel debugger). For example, DbgBreak causes a regular debugger breakpoint, whereas KDbgBreak causes a kernel debugger breakpoint.

Name	Description
DbgBreak	Breakpoint with message box.
DbgBreakPoint	Breakpoint with message box.
KDbgBreak	Breakpoint with message on kernel debugger.

---

DbgBreak

Generates a message box in a debug build with the indicated string literal, the source file name, and the source line number. Buttons in the message box allow you to break into the debugger, kill the application, or ignore the message box.

DbgBreak(
  strLiteral
  );

Parameters

strLiteral

Text string, which must be in quotation marks.

Remarks

This macro is ignored unless DEBUG is defined when the Microsoft® DirectShow™ headers are included.

---

DbgBreakPoint

Generates a message box in a debug build with the indicated string literal, the source file name, and the source line number. Buttons in the message box allow you to break into the debugger, kill the application, or ignore the message box.

void WINAPI DbgBreakPoint(
  const TCHAR *pCondition,
  const TCHAR *pFileName,
  INT iLine
  );

Parameters

pCondition

Pointer to a string indicating what happened.

pFileName

Pointer to a source file name.

iLine

Line number within the source file.

Remarks

This function is available only in a debug build.

---

KDbgBreak

Generates a kernel debugger message in a debug build with the indicated string literal, the source file name, and the source line number.

KDbgBreak(
  strLiteral
  );

Parameters

strLiteral

Text string, which must be in quotation marks.

Remarks

This macro is ignored unless DEBUG is defined when the Microsoft DirectShow headers are included.

© 1997 Microsoft Corporation. All rights reserved. Terms of Use.