Logo Search packages:      
Sourcecode: virtualbox-ose version File versions  Download package

VMM Debug Event Type.

Enumerator:
DBGFEVENT_HALT_DONE  Halt completed. This notifies that a halt command have been successfully completed.
DBGFEVENT_DETACH_DONE  Detach completed. This notifies that the detach command have been successfully completed.
DBGFEVENT_INVALID_COMMAND  The command from the debugger is not recognized. This means internal error or half implemented features.
DBGFEVENT_FATAL_ERROR  Fatal error. This notifies a fatal error in the VMM and that the debugger get's a chance to first hand information about the the problem.
DBGFEVENT_BREAKPOINT  Breakpoint Hit. This notifies that a breakpoint installed by the debugger was hit. The identifier of the breakpoint can be found in the DBGFEVENT::u::Bp::iBp member.
DBGFEVENT_BREAKPOINT_HYPER  Breakpoint Hit in the Hypervisor. This notifies that a breakpoint installed by the debugger was hit. The identifier of the breakpoint can be found in the DBGFEVENT::u::Bp::iBp member.
DBGFEVENT_ASSERTION_HYPER  Assertion in the Hypervisor (breakpoint instruction). This notifies that a breakpoint instruction was hit in the hypervisor context.
DBGFEVENT_STEPPED  Single Stepped. This notifies that a single step operation was completed.
DBGFEVENT_STEPPED_HYPER  Single Stepped. This notifies that a hypervisor single step operation was completed.
DBGFEVENT_DEV_STOP  The developer have used the DBGFSTOP macro or the PDMDeviceDBGFSTOP function to bring up the debugger at a specific place.
DBGFEVENT_TERMINATING  The VM is terminating. When this notification is received, the debugger thread should detach ASAP.
DBGFEVENT_32BIT_HACK  The usual 32-bit hack.

Definition at line 136 of file dbgf.h.

{
    /** Halt completed.
     * This notifies that a halt command have been successfully completed.
     */
    DBGFEVENT_HALT_DONE = 0,
    /** Detach completed.
     * This notifies that the detach command have been successfully completed.
     */
    DBGFEVENT_DETACH_DONE,
    /** The command from the debugger is not recognized.
     * This means internal error or half implemented features.
     */
    DBGFEVENT_INVALID_COMMAND,


    /** Fatal error.
     * This notifies a fatal error in the VMM and that the debugger get's a
     * chance to first hand information about the the problem.
     */
    DBGFEVENT_FATAL_ERROR = 100,
    /** Breakpoint Hit.
     * This notifies that a breakpoint installed by the debugger was hit. The
     * identifier of the breakpoint can be found in the DBGFEVENT::u::Bp::iBp member.
     */
    DBGFEVENT_BREAKPOINT,
    /** Breakpoint Hit in the Hypervisor.
     * This notifies that a breakpoint installed by the debugger was hit. The
     * identifier of the breakpoint can be found in the DBGFEVENT::u::Bp::iBp member.
     */
    DBGFEVENT_BREAKPOINT_HYPER,
    /** Assertion in the Hypervisor (breakpoint instruction).
     * This notifies that a breakpoint instruction was hit in the hypervisor context.
     */
    DBGFEVENT_ASSERTION_HYPER,
    /** Single Stepped.
     * This notifies that a single step operation was completed.
     */
    DBGFEVENT_STEPPED,
    /** Single Stepped.
     * This notifies that a hypervisor single step operation was completed.
     */
    DBGFEVENT_STEPPED_HYPER,
    /** The developer have used the DBGFSTOP macro or the PDMDeviceDBGFSTOP function
     * to bring up the debugger at a specific place.
     */
    DBGFEVENT_DEV_STOP,
    /** The VM is terminating.
     * When this notification is received, the debugger thread should detach ASAP.
     */
    DBGFEVENT_TERMINATING,

    /** The usual 32-bit hack. */
    DBGFEVENT_32BIT_HACK = 0x7fffffff
} DBGFEVENTTYPE;


Generated by  Doxygen 1.6.0   Back to index