How is the Zig Debugger now?

[rickygai]

Windows 11 22H2 (OS Build 22621.6060)
Visual Studio Code v1.143.1
Zig v0.18.0

I checked this forum regarding debugging articles, not much solutions found.

Currently, I tested Zig with options:

zig build-exe -fllvm -target x86_64-windows-gnu -O Debug test.zig -femit-bin=test.exe

zig build-exe -fllvm -target x86_64-windows-msvc -O Debug test.zig -femit-bin=test.exe

and with VSCode launch.json:

"configurations": [
   {
   ...
      "type": "lldb", // also tested "cppvsdbg"
      "request": "launch",
   ...
   }
]

Both “type” of “lldb” and “cppvsdbg” cannot correctly show the variables added under “Watch” panel, I received something like below,

Please advise

[vulpesx]

these threads may be helpful

Debugging Zig (with a debugger)

Debugging Zig code is a bit of a dark art at present:. There’s no official documentation on the subject, and the lore involved is scattered among blog posts, video, Ziggit questions, the Discord, and so on. So I thought I’d start a topic as a place to share knowledge of the dark art. I also want to improve my own workflow here, so I’ll start with what I have working. VSCode and CodeLLDB I do most of my development in Neovim now (I use Neovim btw), but not debugging.. yet. For that I’m using …

Zig Debugging with LLDB

Short example of degugging with LLDB. As an example, I will use a small program that I wrote for Rosetta Code: const std = @import("std"); const stdout = @import("std").io.getStdOut().writer(); pub fn rot(txt: []u8, key: u8) void { for (txt, 0..txt.len) |c, i| { if (std.ascii.isLower(c)) { txt[i] = (c - 'a' + key) % 26 + 'a'; } else if (std.ascii.isUpper(c)) { txt[i] = (c - 'A' + key) % 26 + 'A'; } } } pub fn main() !void { const ke…