3 ms·

I think he means the LLDB console. You can inspect anything, however deeply you want. Create new objects. Assign them to variables. Run code snippets against yo

by emp 14y ago

I think he means the LLDB console. You can inspect anything, however deeply you want. Create new objects. Assign them to variables. Run code snippets against your existing state at the breakpoint. Learn new APIs interactively. Reduce the need to compile/run as often. It's the closest I can get to a Smalltalk Workspace/Transcript. I agree that the GUI debugger is limited, and after living in the console for some time, next to useless.

to3m 14y ago
I use lldb from Xcode, but I don't use the GUI part, because it's worse than useless. The command line is better, but not by THAT much. It seems to regularly get confused by debug info, so if it fails to tell you "no member info found due to forward declaration of struct XXX" (or something similar) when you're trying to print a local value of type XXX, you'll just get gibberish. Then sometimes it just dies when stepping over function calls. Something I found today: "p/x $rip" will show you the PC, but "break set -a $rip" won't set a breakpoint there, because lldb can't figure out what $rip means. The online help is also not very helpful.