forked from OSchip/llvm-project
738af7a624
For example, it is pretty easy to write a breakpoint command that implements "stop when my caller is Foo", and
it is pretty easy to write a breakpoint command that implements "stop when my caller is Bar". But there's no
way to write a generic "stop when my caller is..." function, and then specify the caller when you add the
command to a breakpoint.
With this patch, you can pass this data in a SBStructuredData dictionary. That will get stored in
the PythonCommandBaton for the breakpoint, and passed to the implementation function (if it has the right
signature) when the breakpoint is hit. Then in lldb, you can say:
(lldb) break com add -F caller_is -k caller_name -v Foo
More generally this will allow us to write reusable Python breakpoint commands.
Differential Revision: https://reviews.llvm.org/D68671
|
||
|---|---|---|
| .. | ||
| address_breakpoints | ||
| auto_continue | ||
| breakpoint_by_line_and_column | ||
| breakpoint_command | ||
| breakpoint_conditions | ||
| breakpoint_hit_count | ||
| breakpoint_ids | ||
| breakpoint_ignore_count | ||
| breakpoint_in_delayslot | ||
| breakpoint_language | ||
| breakpoint_locations | ||
| breakpoint_names | ||
| breakpoint_options | ||
| breakpoint_set_restart | ||
| comp_dir_symlink | ||
| consecutive_breakpoints | ||
| cpp | ||
| cpp_exception | ||
| debugbreak | ||
| dummy_target_breakpoints | ||
| global_constructor | ||
| hardware_breakpoints/hardware_breakpoint_on_multiple_threads | ||
| inlined_breakpoints | ||
| move_nearest | ||
| objc | ||
| require_hw_breakpoints | ||
| scripted_bkpt | ||
| serialize | ||
| source_regexp | ||
| step_over_breakpoint | ||