MCPcopy Create free account
hub / github.com/Vector35/debugger / step_over

Method step_over

api/python/debuggercontroller.py:853–872  ·  view source on GitHub ↗

Perform a step over on the target. When the next instruction is not a call, execute the next instruction. When the next instruction is a call, complete the execution of the function and break at next instruction. The operation can be performed on an IL level specif

(self, il: binaryninja.FunctionGraphType = binaryninja.FunctionGraphType.NormalFunctionGraph)

Source from the content-addressed store, hash-verified

851 return dbgcore.BNDebuggerStepInto(self.handle, il)
852
853 def step_over(self, il: binaryninja.FunctionGraphType = binaryninja.FunctionGraphType.NormalFunctionGraph) -> bool:
854 """
855 Perform a step over on the target.
856
857 When the next instruction is not a call, execute the next instruction. When the next instruction is a call,
858 complete the execution of the function and break at next instruction.
859
860 The operation can be performed on an IL level specified by the ``il`` parameter, which then either executes the
861 next IL instruction, or completes the IL function. Note, the underlying operation is still performed at the
862 disassembly level because that is the only thing a debugger understands. The high-level operations are simulated
863 on top of the disassembly and analysis.
864
865 Some limitations are known with stepping over on IL.
866
867 The call is asynchronous and returns before the target stops.
868
869 :param il: optional IL level to perform the operation at
870 :return: the reason for the stop
871 """
872 return dbgcore.BNDebuggerStepOver(self.handle, il)
873
874 def step_return(self) -> bool:
875 """

Callers

nothing calls this directly

Calls

no outgoing calls

Tested by

no test coverage detected