Compatibility Challenges with Zig Language Extras on Windows 10 LTSC Using MinGW-W64 and Scoop and Ubuntu 23.10

[punowo]

Hello. First of all thank you for this extension. I've wanted something like this for a while. ziglang/vscode-zig#158

I'm having some trouble getting this to work and this might be due to my somewhat unorthodox setup, I say this because from what I've seen most people just use msvc on Windows.

I am on Windows 10 LTSC and I pull mingw-winlibs-llvm-ucrt-mcf ( gcc, gdb ), zig and zls from scoop ( https://scoop.sh/ ). With C/C++ I just use handle everything through the cmake vscode plugin which has the ability to initialize projects, debug cmake files and even Cmake: Debug which just works no matter what OS I'm on as long as there a C/C++ compiler present.

PS C:\Users\pun> gcc --version
gcc.exe (MinGW-W64 x86_64-ucrt-mcf-seh, built by Brecht Sanders) 13.2.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

PS C:\Users\pun> gdb --version
GNU gdb (GDB for MinGW-W64 x86_64, built by Brecht Sanders) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

PS C:\Users\pun> zig version
0.11.0

I've made a simple hello type test project.

Here are the results for each respective "zig-language-extras.debugType" option:

cppvsdbg

gdb

lldb

I can getting working by having the project name be main with the default option for win32, cppvsdbg.

[ianic]

Uf, Windows... never tried it there.

Please look at #3 where @Niakr1s introduced Windows support.
Maybe you can set 'zig-language-extras.debugType' to your debugger.

Ooo, sorry, just saw that you already tried various debugTypes.

[ianic]

Can you manually build launch config, this is what extension does.
Then start with launch config from extensions and then tweak it to work with different debuggers.

binPath can be found in extension output.

[punowo]

I can manually build launch configs. I think the problem is how the binPath is generated.

zig-language-extras/src/extension.ts

Line 183 in 6fd6048

let binName = path.parse(fileNameRelative).name;

I say this because I've tried debugging the extension and it never enters that if unless you use .base instead of .name.

Now, I know practically nothing about Zig ( still learning ) and this is the first time I've tried to debug a vscode extension but what happens when you try to start Zig Extras: Debug Binary from a file that is not main.zig but has something that is called / required in main.zig ?

[punowo]

Hi. I'm having the same problem on Ubuntu 23.10.

I do believe at this point there's something wrong with how the binary path is constructed. Is anyone else having this problem ?

[punowo]

Hi. I made a pull request that solves the problem I am facing but I don't know if it's exactly what is needed. Despite the formatting changes I only added two functions at the top and changed the how binary path is generated inside the "Debug Binary" part of the code.

#6

[ianic]

Thanks for your effort in bringing this up.

When debugging binary, extension tries to decide on binary name in zig-out/bin folder. That should be name of the file or for main.zig name of the parent folder (skipping src). I found a problem in that logic.

Could you please try with the latest 0.62 version.

[punowo]

I don't have access to my windows machine but I'm pretty sure you can close this. The problem is fixed for me on my Ubuntu 23.10 machine. Thanks for the update.