DBG C ClearWatch: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 13: | Line 13: | ||
If a debugger wishes to move a watchpoint from one location to another, it should clear the old watchpoint before setting the new one, to free any resources used by currently set watchpoints. | If a debugger wishes to move a watchpoint from one location to another, it should clear the old watchpoint before setting the new one, to free any resources used by currently set watchpoints. | ||
The watchpoint will be cleared even if it is currently hit, and a notification is pending. To prevent missing the watchpoint hit in this way, you should issue the DBG_C_Stop command just before clearing the watchpoint, to pick up any pending watchpoint hit notifications. | The watchpoint will be cleared even if it is currently hit, and a notification is pending. To prevent missing the watchpoint hit in this way, you should issue the [[DBG_C_Stop]] command just before clearing the watchpoint, to pick up any pending watchpoint hit notifications. | ||
[[Category:DBG_C]] | [[Category:DBG_C]] | ||
{{DISPLAYTITLE:DBG_C_ClearWatch}} | {{DISPLAYTITLE:DBG_C_ClearWatch}} | ||
Revision as of 12:14, 10 March 2020
Debug Command 25 - Clear Watchpoint Command
- Parameters
- Pid= Process ID of debuggee
- Cmd= DBG_C_ClearWatch
- Index= Watchpoint ID Number
- Returns
This command clears a currently set or hit watchpoint.
If the watchpoint is not currently set, an error is returned.
If a debugger wishes to move a watchpoint from one location to another, it should clear the old watchpoint before setting the new one, to free any resources used by currently set watchpoints.
The watchpoint will be cleared even if it is currently hit, and a notification is pending. To prevent missing the watchpoint hit in this way, you should issue the DBG_C_Stop command just before clearing the watchpoint, to pick up any pending watchpoint hit notifications.