In a situation where you have a lot of breakpoints set, some enabled and some not, and you want to continue till you hit one breakpoint but don't want to hit any of the others in the course of doing that, you have to hand disable the other breakpoints, then continue, then re-enable the ones that were enabled when you started (but not the others). That's tedious but easily done with scripting. I wrote up this little example for somebody and it seems generally useful.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lldb/examples/python/cont_to_bkpt.py | ||
---|---|---|
5–6 | Are these properties needed by lldb? They aren't used in __call__. |
Just trying to be helpful!
lldb/examples/python/cont_to_bkpt.py | ||
---|---|---|
26 | Reuse target here rather than exe_ctx.target? |
The patch gets a little hard to read with all the no-longer in the right places comments, but I think I addressed everything.
The patch gets a little hard to read with all the no-longer in the right places comments
I just learned there's a keyboard shortcut (A) that hides them all.
lldb/examples/python/cont_to_bkpt.py | ||
---|---|---|
6 | Nit: The "Pythonic" way of doing is using pass |
Are these properties needed by lldb? They aren't used in __call__.