breakpoints: use lldb breakpoints

.pre-commit-config.yaml

@@ -11,5 +11,5 @@ repos:
     rev: "7.0.0"
     hooks:
       - id: flake8
-        args: [ '--max-complexity=14', '--max-line-length=127' ]
+        args: [ '--max-complexity=18', '--max-line-length=127' ]
         files: \.py$

README.md

@@ -152,7 +152,7 @@ Here is a gist of methods you can access from `p`:
   - Simulate a call to an objc selector
 - `call`
   - Call function at given address with given parameters
-- `monitor`
+- `monitor` or `breakpoints.add_monitor`
   - Monitor every time a given address is called
 
       The following options are available:
@@ -197,21 +197,21 @@ Here is a gist of methods you can access from `p`:
   - Step into current instruction.
 - `step_over`
   - Step over current instruction.
-- `remove_all_hilda_breakpoints`
-  - Remove all breakpoints created by Hilda
-- `remove_hilda_breakpoint`
-  - Remove a single breakpoint placed by Hilda
+- `breakpoints.clear`
+  - Remove all breakpoints
+- `breakpoints.remove`
+  - Remove a single breakpoint
 - `force_return`
   - Prematurely return from a stack frame, short-circuiting exection of newer frames and optionally
       yielding a specified value.
 - `proc_info`
   - Print information about currently running mapped process.
 - `print_proc_entitlements`
   - Get the plist embedded inside the process' __LINKEDIT section.
-- `bp`
+- `bp` or `breakpoints.add`
   - Add a breakpoint
-- `show_hilda_breakpoints`
-  - Show existing breakpoints created by Hilda.
+- `breakpoints.show`
+  - Show existing breakpoints
 - `save`
   - Save loaded symbols map (for loading later using the load() command)
 - `load`
@@ -474,7 +474,7 @@ s.bp(scripted_breakpoint)
 p.bp('symbol_name')
 
 # In case you need to specify a specific library it's loaded from
-p.bp('symbol_name', module_name='ModuleName')
+p.bp(('symbol_name', 'ModuleName'))
 ```
 
 #### Globalized symbols