radare2

mirror of https://github.com/radareorg/radare2.git synced 2024-12-12 07:26:42 +00:00

History

pancake d64b876e73 * Fix build * Add some more hud commands		2012-01-31 03:42:27 +01:00
..
p	* brainfuck debugger is finally usable	2011-10-09 04:15:32 +02:00
bp.c	* Various gcc-4.6 warnings fixed	2011-06-30 00:17:12 +02:00
io.c	* Remove debugging printfs in the debugger	2011-07-06 01:45:45 +02:00
Makefile	* Rename "handler" to "plugin"	2010-05-26 18:25:35 +02:00
parser.c
parser.h
plugin.c	* Use RList in r_bp	2010-06-30 01:13:09 +02:00
README	* Initial working implementation of software breakpoints	2010-01-21 02:38:52 +01:00
traptrace.c	* Fix build	2012-01-31 03:42:27 +01:00
watch.c	* Fix segfault in r_bp_get_bytes when used in loops	2010-03-03 13:34:38 +01:00

README

libr.bp
=======

Breakpoint API

- Manages list of defined breakpoints
- Determines if a stop is caused by a breakpoint
- Owns a database of multiple types of breakpoints
  - arch and os based ones
  - Supports endianness
  - r_bp_get should return a buffer and a length
- Manages conditional breakpoints expressions
- Types of breakpoints
  - software (traps)
  - conditional traps
  - hardware (registers)
  - mmu (changes page protections)
- All non-native operations are translated into evaluable expressions
  by other modules. Like changing register values and so on
  - Do we should place some callbacks for this kind of ops?
- We need to make this work also remotely
  - r_debug can handle the remoteness of the debugger backend.
  - r_io can do it also
- Watchpoints and its exception should be handled here
  - watchpoint expressions should be handled by using the r_num stuff
- Hardware breakpoints require access to registers, or pid/tid
  this is... the debugger backend. For those, the debugger backend
  should fill a callback to manage them.
  - if the debugger breakpoint handler does not manages the breakpoint
    type, r_bp must do it with r_io storing and loading bp bytes.

* Do we need the plugin API to define new breakpoints and so on?