Debugging Tools for Windows |
The Breakpoints section enables you to define the breakpoints that you want to monitor and to configure the actions that you want the debugger to take when these breakpoints are hit.
<NewBP>
<Address> Address </Address>
<Type> { BP | BU | BM } </Type>
<Passes> Passes </Passes>
<Actions> Actions </Actions>
<CustomActions> CustomActions </CustomActions>
<ReturnAction> { G | Q | QD } </ReturnAction>
</NewBP>
<Config>
<Address> { Address | AllBreakpoints } </Address>
<Actions> Actions </Actions>
<CustomActions> CustomActions </CustomActions>
<ReturnAction> { G | Q | QD } </ReturnAction>
</Config>
</Breakpoints>
The <NewBP> tag enables you to define new breakpoints. The <Config> tag enables you to define the behavior for breakpoints that are already defined.
All of the subtags of <NewBP> and <Config> are optional, except for <Address>.
You can use the following parameters:
If you use BM, you can define multiple breakpoints at the same time by using wildcard characters in the address. For example, you could define the address as Advapi32!Crypt*. This syntax creates a breakpoint in all functions in Advapi32.dll that begin with Crypt.
You can use the following case-sensitive actions: