As Jim said, we have many different kinds of breakpoints and breakpoints can
have N SBBreakpointLocations and that number can change as your process runs
and more shared libraries are loaded.
If you set a source file and line breakpoint to begin with, then iterating over
the locations is the be
A breakpoint doesn’t necessarily have a file & line number. Remember that
breakpoints in lldb really are “search kernels” - called “Resolvers" and one
breakpoint’s resolver can match any number of locations in code. As an extreme
instance “break set -r .*” will match many many functions… So t
I've been trying to get at the file path, line and column information of a
break point via the python API but have been struggling.
given the following method :
def do_thing_with_bp_in_file_on_line(file_path, line_no):
... do something with breakpoints on line_no in file at file_path
what woul
