Using Action Points
Action points stop a program’s execution. You can specify the following types of action points:
A barrierpoint (seedbarrier) prevents processes from proceeding beyond a point until all other related processes arrive. This gives you a method for synchronizing the activities of processes. (You can set a barrierpoint only on processes; you cannot set then on individual threads.)An evalpoint (seedbreak) supports the programmatic evaluation of the state of the process or variable when execution reaches a location in the source code. An evalpoint is usually used to stop the process when some condition that you specify is met.Each action point is associated with an action point identifier, used when you need to refer to the action point. Like process and thread identifiers, action point identifiers are assigned numbers as they are created. The ID of the first action point created is 1, the second ID is 2, and so on. These numbers are never reused during a debugging session.
The CLI and the UI allow the assignment of only one action point to a source code line.
