forked from OSchip/llvm-project
b842f2ecf0
When introduced, breakpoint names were just tags that you could apply to breakpoints that would allow you to refer to a breakpoint when you couldn't capture the ID, or to refer to a collection of breakpoints. This change makes the names independent holders of breakpoint options that you can then apply to breakpoints when you add the name to the breakpoint. It adds the "breakpoint name configure" command to set up or reconfigure breakpoint names. There is also full support for then in the SB API, including a new SBBreakpointName class. The connection between the name and the breakpoints sharing the name remains live, so if you reconfigure the name, all the breakpoint options all change as well. This allows a quick way to share complex breakpoint behavior among a bunch of breakpoints, and a convenient way to iterate on the set. You can also create a name from a breakpoint, allowing a quick way to copy options from one breakpoint to another. I also added the ability to make hidden and delete/disable protected names. When applied to a breakpoint, you will only be able to list, delete or disable that breakpoint if you refer to it explicitly by ID. This feature will allow GUI's that need to use breakpoints for their own purposes to keep their breakpoints from getting accidentally disabled or deleted. <rdar://problem/22094452> llvm-svn: 313292 |
||
|---|---|---|
| .. | ||
| android | ||
| modules | ||
| finish-swig-Python-LLDB.sh | ||
| finishSwigPythonLLDB.py | ||
| modify-python-lldb.py | ||
| prepare_binding_Python.py | ||
| python-extensions.swig | ||
| python-swigsafecast.swig | ||
| python-typemaps.swig | ||
| python-wrapper.swig | ||
| remote-build.py | ||
| use_lldb_suite.py | ||