stopi (idb mode only)

Set a breakpoint at an instruction, or if a variable changes.

Syntax

stopi [traced_expression] [thread ID ,...] [at address] [if cond]
stopi address [thread id ,...] [if cond]

Parameters

`traced_expression`	An expression that you want to trace.
`ID`	A thread ID.
`address`	An address. When using the form `stopi address`, this value is an integer constant.
`cond`	A conditional expression.

Description

This command sets a breakpoint at an instruction or on a traced expression.

If you specify traced_expression, program execution stops when the value of the traced expression changes.

If you specify if cond, program execution stops when cond evaluates to true.

If you specify both traced_expression and if cond, program execution stops only if cond evaluates to true and the value of traced_expression has changed.

If you specify at address, program execution stops when it hits address.

If you specify both traced_expression and at address, program execution stops only if the variable has changed when the address is hit.

If you specify both at address and if cond, execution stops only if cond evaluates to true when the address is hit.

If you specify traced_expression, at address, and if cond, execution stops only if the value of traced_expression has changed and if cond evaluates to true when the address is hit.

Specify the thread list to set tracepoints in specific threads. If you list one or more thread IDs, the debugger sets a tracepoint only in those threads you specify. If you do not specify a thread ID, the debugger sets a tracepoint in all the threads of the application.

The stopi command differs from the stop command in that the debugger checks the breakpoint set with the stopi command after executing each machine instruction. So using stopi affects performance of the debuggee.