I have a simple Zig program that can be successfully debugged by VS2019 but not by RemedyBG.
1 2 3 4 5 6 7 8 9 10 | const std = @import("std"); pub fn main() !void { // If this program is run without stdout attached, exit with an error const stdout_file = try std.io.getStdOut(); // If this program encounters pipe failure when printing to stdout, exit // with an error. try stdout_file.write("Hello, world!\n"); } |
The problematic behavior is clear to see below. For some reason, RemedyBG cannot manage to find the breakpoints placed on those lines of code while VS2019 can.
I know the majority of users who use RemedyBG do so to debug C code, but given that VS2019 can work with Zig PDB files, I think RemedyBG should too. Do you consider this a bug to be fixed?
https://vimeo.com/366008013
https://vimeo.com/366008003
I have sent a zip file containing the Zig code and pdb files to your email. This thread is for public awareness.
Thanks,
Jesse