Skip to content
This repository was archived by the owner on Feb 20, 2024. It is now read-only.

Conversation

@bluehazzard
Copy link
Contributor

This pull request extends the debugger with memory range watches
http://forums.codeblocks.org/index.php/topic,21457.30.html

in addition it fixes a bug where debugger events are not fired
cb92b4a and adds additional debugger events that are needed for a complete debugger session detection
4c621f1 and 5240fe6

Fire the event if the debugger is paused and no future commands are in the queue.
Don't send debugger commands within this event, or you will end in a endless loop
Fire the event if the debugger is restarted by the user or a command
Implement AddMemoryRange and modify DeleteWatch and HasWatch to be aware
of memory watches
Implement
* SetMemoryRangeValue():
Set a memory range from start address
to x bytes at the value given in "value" parameter. The value is stored
as binary and can be retrieved from "value" with wxString::To8BitData()
and passed to "value" with wxString::From8BitData()

* UpdateMemoryRangeWatches()
* UpdateMemoryRangeWatch()
Read the value of the memory at the specified address and update the
watch accordingly
For this functions only stubs exist:
SetMemoryRangeValue()
UpdateMemoryRangeWatches()
UpdateMemoryRangeWatch()
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant