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.
DbgBreak | Generates a message box in a debug build with the indicated string literal. |
DbgBreakPoint | Generates a message box in a debug build with the indicated string literal, the source file name, and the source line number. |
KDbgBreak | Generates a kernel debugger message in a debug build with the indicated string literal, the source file name, and the source line number. |
Generates a message box in a debug build with the indicated string literal. Buttons in the message box enable you to break into the debugger, quit the application, or ignore the message box.
Syntax
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.
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 enable you to break into the debugger, quit the application, or ignore the message box.
Syntax
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.
Generates a kernel debugger message in a debug build with the indicated string literal, the source file name, and the source line number.
Syntax
KDbgBreak( strLiteral );
Parameters
- strLiteral
- Text string, which must be in quotation marks.
Remarks
This macro is ignored unless DEBUG is defined when the DirectShow headers are included.
Top of Page
© 2000 Microsoft and/or its suppliers. All rights reserved. Terms of Use.