Is there any combination of OS/Debugger/build configuration where zig debugging fully works, i.e., in-scope variables are always correctly visible? I've tried a few combinations recently (win11 + forcing the llvm backend + rad debugger, vscode + lldb, vscode + cppvsdbg, zed + lldb), and linux in the past. I can get a reasonable experience with most of these, but haven't found a combination that always works to show locals (win11 + force llvm backend + vscode + cppvsdbg is the best so far). Curious if there is a generally working solution I've just missed. Also more than happy to switch back to linux if that's a better experience, though I've been waiting for raddbg to land there. TIY.
#Debugging - which tools/OS combination currently provides the best experience (Jan 2026)
sharp yarrow
final harbor
You didn't mention trying JacoblyO's lldb fork.
tough monolith
I would say linux + custom backend in debug + lldb fork mentioned
everything else should have the same issues as with llvm zig pretends to be cpp.
sharp yarrow
Ack, thanks. I haven't tried https://github.com/jacobly0/llvm-project/tree/lldb-zig yet, will try that next and add an update here with how it goes. My understanding is to use it with the (now-default for debug builds) custom backend rather than llvm.
