| UID | title | description | old-location | tech.root | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NF:wdm.DbgBreakPointWithStatus |
DbgBreakPointWithStatus function (wdm.h) |
The DbgBreakPointWithStatus routine breaks into the kernel debugger and sends the value of Status to the debugger. |
devtest\dbgbreakpointwithstatus.htm |
devtest |
02/23/2018 |
|
DbgBreakPointWithStatus, DbgBreakPointWithStatus routine [Driver Development Tools], DebugFns_d958e007-b135-46b0-a407-1843da2e61c0.xml, devtest.dbgbreakpointwithstatus, ntddk/DbgBreakPointWithStatus |
wdm.h |
Wdm.h, Ntddk.h |
Universal |
Available in Microsoft Windows 2000 and later. |
DebugBreakUsage |
Ntdll.lib (user mode); NtosKrnl.lib (kernel mode) |
NtosKrnl.exe |
Windows |
|
|
|
|
|
The DbgBreakPointWithStatus routine breaks into the kernel debugger and sends the value of Status to the debugger.
Specifies a ULONG value that is sent to the debugger (for example, a status code or an address).
None
DbgBreakPointWithStatus is identical to DbgBreakPoint, except for the Status message.
On x86 computers, the Status parameter is stored in the eax register. On machines that have register calling conventions, Status is stored in the first argument register.
This routine raises an exception that is handled by the kernel debugger if one is installed; otherwise it is handled by the debug system. If a debugger is not connected to the system, the exception can be handled in the standard way.
In kernel mode, a break exception that is not handled will cause a bug check. You can, however, connect a kernel-mode debugger to a target computer that has stopped responding and has kernel debugging enabled. For more information, see Windows Debugging.