rizin

History

Nibble ab956379ea * Fixed plugin name length error in r_{asm, anal, lang} * r_asm - asm_bea renamed to asm_x86_bea - asm_olly renamed to asm_x86_olly - Minor fixups in rasm2 * r_debug - R_ASM_ARCH_ renamed to R_DBG_ARCH_ --HG-- rename : libr/asm/p/asm_bea.c => libr/asm/p/asm_x86_bea.c rename : libr/asm/p/asm_olly.c => libr/asm/p/asm_x86_olly.c		2009-02-19 16:41:51 +01:00
..
p	* Initial working implementation of the debugger mode	2009-02-18 01:43:57 +01:00
debug.c	* Fixed plugin name length error in r_{asm, anal, lang}	2009-02-19 16:41:51 +01:00
handle.c	* Initial working implementation of the debugger mode	2009-02-18 01:43:57 +01:00
Makefile	* Initial import of libr	2009-02-05 22:08:46 +01:00
README	* Lot of random work on multiple fronts	2009-02-17 00:09:40 +01:00

README

r_debug
=======

  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 allows 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)