radare2

mirror of https://github.com/radareorg/radare2.git synced 2024-12-02 02:06:46 +00:00

History

pancake e5799fb7a2 Fix build on linux-mipsel64 - debugger backend now sets dbg.swstep - define linux-mips64 register profile - fix 32/64 annoyance in debugger - fix register read under some situations		2012-07-05 16:02:12 +00:00
..
p	Fix build on linux-mipsel64	2012-07-05 16:02:12 +00:00
bp.c	* More split of core/cmd.c	2012-02-27 03:07:32 +01:00
io.c
Makefile
parser.c
parser.h
plugin.c
README
traptrace.c	* Use r_list_foreach[_safe] where appropriate.	2012-02-14 18:19:16 +01:00
watch.c

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?