Print statements are a fine debugger until the day they are not. When you need the real thing, Codeworks launches LLDB, the debugger at the heart of the Apple toolchain.
The loop is all there. Set breakpoints in the gutter, launch, and step through code. Inspect the call stack, walk frames, and read variables as they change. Console output lands in the workspace, next to the code that produced it.
Why LLDB specifically. It is the debugger your platform already trusts, actively maintained, and deeply capable. Building on it means Codeworks’s debugging grows with the toolchain instead of drifting from it.
Debugging in the same window you edit in closes a loop: read, suspect, break, step, confirm, fix. The shorter that loop, the sooner you are back to the part of programming you actually enjoy.