44 Chapter 7. Stopping and ContinuingNo symbol "foo" in current context.gdb does not actually evaluate expression at the time the condition command (or a com-mand that sets a breakpoint with a condition, like break if ...) is given, however. Refer toSection 10.1 Expressions.condition bnumRemove the condition from breakpoint number bnum. It becomes an ordinary unconditionalbreakpoint.A special case of a breakpoint condition is to stop only when the breakpoint has been reached a certainnumber of times. This is so useful that there is a special way to do it, using the ignore count of thebreakpoint. Every breakpoint has an ignore count, which is an integer. Most of the time, the ignorecount is zero, and therefore has no effect. But if your program reaches a breakpoint whose ignorecount is positive, then instead of stopping, it just decrements the ignore count by one and continues.As a result, if the ignore count value is n, the breakpoint does not stop the next n times your programreaches it.ignore bnum countSet the ignore count of breakpoint number bnum to count. The next count times the breakpointis reached, your program’s execution does not stop; other than to decrement the ignore count,gdb takes no action.To make the breakpoint stop the next time it is reached, specify a count of zero.When you use continue to resume execution of your program from a breakpoint, you canspecify an ignore count directly as an argument to continue, rather than using ignore. Referto Section 7.2 Continuing and stepping.If a breakpoint has a positive ignore count and a condition, the condition is not checked. Oncethe ignore count reaches zero, gdb resumes checking the condition.You could achieve the effect of the ignore count with a condition such as $foo- = 0 using adebugger convenience variable that is decremented each time. Refer to Section 10.9 Conveniencevariables.Ignore counts apply to breakpoints, watchpoints, and catchpoints.7.1.7. Breakpoint command listsYou can give any breakpoint (or watchpoint or catchpoint) a series of commands to execute whenyour program stops due to that breakpoint. For example, you might want to print the values of certainexpressions, or enable other breakpoints.commands [bnum]... command-list ...endSpecify a list of commands for breakpoint number bnum. The commands themselves appear onthe following lines. Type a line containing just end to terminate the commands.To remove all commands from a breakpoint, type commands and follow it immediately with end;that is, give no commands.With no bnum argument, commands refers to the last breakpoint, watchpoint, or catchpoint set(not to the breakpoint most recently encountered).Pressing [RET] as a means of repeating the last gdb command is disabled within a command-list.
