gc (Go from Conditional Breakpoint)

The gc command resumes execution from a conditional breakpoint in the same fashion that was used to hit the breakpoint (stepping, tracing, or freely executing). This only applies to the older style of conditional breakpoints using a "j (Condition) ..." style expression, rather than the simpler "/w" style conditional breakpoint. For more information, see setting a conditional breakpoint.

gc

While this command is no longer as useful for conditional breakpoints, it can still be used for breakpoints that do logging or some other activity without breaking into the debugger. For instance, a breakpoint could be written that looks like this:

bp module!myFunction ".echo myFunction executed; gc"

If a normal "g" command were used instead, the program would continue execution when stepping over "myFunction", instead of simply printing the message and continuing the step operation.

Environment

Item	Description
Modes	user mode, kernel mode
Targets	live debugging only
Platforms	all

Additional Information

For an overview of related commands, see Controlling the Target.

Remarks

When a conditional breakpoint using a "j (Condition) ..." expression includes an execution command at the end, this should be the gc command.

For example, the following is an example conditional breakpoint:

0:000> bp Address "j (Condition) 'OptionalCommands'; 'gc' " 

When this breakpoint is encountered and the expression is false, execution will resume using the same execution type that was previously used. For example, if you used a g (Go) command to reach this breakpoint, execution would resume freely. But if you reached this breakpoint while stepping or tracing, execution would resume with a step or a trace.

On the other hand, the following is an improper breakpoint formulation, since execution will always resume freely even if you had been stepping before reaching the breakpoint:

0:000> bp Address "j (Condition) 'OptionalCommands'; 'g' "