Catch lldb's breakpoint command to display them in source

[sakhnik]

Catch lldb's breakpoint command to display them in source

[FrankBro]

Maybe it's worth to open multiple bugs but I realized it does not catch commands such as up either. Meaning it does not start pointing in the file you have opened.

[FrankBro]

Can confirm it also does not work on gdb.
break X will set it, F8 on the line it should be will remove it, pressing F8 again will set it and display it.

[sakhnik]

That's quite expected, I already considered this in #7. For the plugin to capture a breakpoint set without F8, it's required to parse GDB/LLDB output as of today's implementation. This is neither accurate nor reliable. For instance, LLDB output wouldn't allow telling a one-shot breakpoint from another one; the file basename isn't enough to pick up a correct source (full path isn't printed though) etc. So actually, I'm investigating how to run GDB and LLDB wrapped into a proxy application with a side-channel for auxiliary commands like "query all the breakpoints in the current file". See #20

Now, more specifically:

• It should work in GDB already. There is already test for that in test_10_detect. If you could create a minimal example how to reproduce the bug, I'd appreciate it.
• LLDB is likely to be supported slightly later than GDB, after #20.

[sakhnik]

By the way, "up" works for me too. Are you sure you don't have any specific LLDB customizations?

[FrankBro]

Ouch, sorry about the last one, forgot to do the debug build. up works for me too. Tested on gdb. 😅