Share via


IeXdi2Exec::SingleStep (Windows CE 5.0)

Send Feedback

This method commands the debugging target to execute a single instruction and then halt again.

HRESULT SingleStep(  BOOL fIgnoreCurrentExcept,  BOOLfOneCycleOnly);

Parameters

  • fIgnoreCurrentExcept
    [in] Indicator that, if TRUE, prevents the probe from catching a potential exception at the current location.

    The debugger uses this indicator to pass the exception to the OS or perform a Go Unhandled instruction.

  • fOneCycleOnly
    [in] Indicator that, if TRUE, causes the target to execute a single step for one clock cycle only.

    If FALSE, this indicator causes the target to execute a single step of one entire instruction.

Return Values

The following table shows return values for this method.

Value Description
S_OK Indicates the function was successful.
E_FAIL Indicates an unspecified failure.
E_INVALIDARG Indicates one or more invalid arguments.
EXDI_E_COMMUNICATION Indicates a communication error between host driver and debugging target.
EXDI_E_TGTWASNOTHALTED Indicates the target was not halted.
EXDI_E_NORESAVAILABLE Indicates that no resource was available to do Single Step.

This message can indicate one of the following:

  • No direct on-chip support
  • No breakpoint resource
  • No Single Step support

Requirements

OS Version: Windows CE 5.0 and later.
Header: eXDI2.h.
Link Library: ole32.lib, oleaut32.lib.

See Also

IeXDI2 Interfaces

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.