pancake fc9301b14b Add hints and named print formats and more
Initial implementation of anal hints (ah?)
Use anal hints in core/disasm. Needs more work
New data structure StrHT (string hashtable)
Simplify core/libs.c with cpp macros
Added r_cons_color() wip function for ansi256 consoles
RPrint no longer depends on r_cons
Sort 'a?' help commands
Add support for named print formats with pf$ command
Add support for 64 bit string pointers in 'pf' ('S')
Add r_print_mute and r_print_format_length functions
Bump r2 nodejs bindings version number
Merge r_print into r_util
2013-01-22 05:06:12 +01:00
..
2012-10-04 01:20:00 +02:00
2010-06-30 01:13:09 +02:00

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?