|Home > Iris APIs > Breakpoints|
Clients manipulate breakpoints in the instance by using the
Clients are encouraged to use the
breakpoint_getList() function to display all breakpoints, instead of maintaining their own list of breakpoints. This ensures that breakpoints that are set by other clients are visible to the user, and avoids the program stopping on invisible and undeletable breakpoints. The use of
breakpoint_getAdditionalConditions() is exotic.
Breakpoints are specific to the target instance that contains them, not to the client that sets them. Breakpoint ids are specific to the instance.
The target instance implementation must ensure that after a breakpoint is hit, which stops the simulation time, it is not immediately hit again when resuming the simulation time, for example by implementing a micro step.
Instances that support the breakpoint interface must also support the event
interface. This allows clients to enable
for an instance.
Debug accesses do not trigger breakpoints.
IRIS_STATE_CHANGED event is generated when a breakpoint list