mirror of
https://github.com/radareorg/radare2.git
synced 2024-12-08 21:47:12 +00:00
13774c2bd5
* Initial blind implementation of w32 debugger - r_cons now handles ^C in w32 console - not yet tested, just blind code typing * Implement 'dp' command to list processes (pids) - Implemented RDebugPid stuff - dp=394 # is used to attach - dp 0 # to list all attachable pids - dp # list current used pid * Added not-yet-implemented threads() callback in RDebugHandle * Fix r_list_free callback handler * Fix again the 'dr=' command :/ * Cleanup the help of 'd?' and 'dm', 'dp' * Use -O2 by default ? |
||
|---|---|---|
| .. | ||
| p | ||
| t | ||
| arg.c | ||
| debug.c | ||
| handle.c | ||
| Makefile | ||
| map.c | ||
| pid.c | ||
| README | ||
| reg.c | ||
Debugger API for radare2
========================
We need to connect multiple pieces...
debugger engine: vm, qemu, bochs, ptrace, mach, w32dbg...
controlflow commands: (should be splitted in two layers)
- continue -- low level
- step -- low level
- trace --- high level one
- ...
the control flow commands depend on other stuff to decide
how to work..this is for example if the arch doesnt supports
continuation, we should provide a step based continue. The
same when a watchpoint is activated and the arch didnt
supports hardware regs for this purpose.
We also need a load/store/dump/restore functions to move the
program from one engine to another (ptrace -> qemu).. we should
provide a way for all this operations between them.
[continue]
|--- check if bp api allow us to continue or we should step into..
|--- check if debug plugin supports continue
[getregs]
|--- r_reg give us a list of registers
| - dr (show bitsize debug registers) // 32 by default
| - dr 32 (show 32 bit debug registers) // depends on size
| - dr:eax (show 'eax' register value)
| - dr:al (show 8bit register 'al')
| - dr eax=33 (set 'eax' register value)