Share via


IeXdi2Exec::SingleStep (Windows Embedded CE 6.0)

1/5/2010

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

Syntax

HRESULT SingleStep(
  BOOL fIgnoreCurrentExcept,
  BOOL   fOneCycleOnly
);

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 Value

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

Header eXDI2.h
Library ole32.lib, oleaut32.lib
Windows Embedded CE Windows CE 5.0 and later

See Also

Reference

IeXdi2Exec
IeXDI2 Interfaces