@doitsujin
Thanks for your replay, it seems that winedbg and its' gdb mode can't recognize symbols embed into compiled dlls.

I finally figured out the best way for me.

Just use way 4 I mentioned above.

Still don't know why I got glob could not process pattern '(null)' error message, this error shows up on gdbserver 8.1 even tried on Windows. Don't have too much time diging into gdb source code, so I change to an older version of 7.1, this time I can launch and debug the target program successfully.

Here're some steps in brief:

1. Configure wineconsole's PATH environment variable, add the path where gdbserver.exe located, the registry key is [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment]

2. After that just follow the guide I mentioned above, use command like gdbserver localhost:3456 loader.exe in wineconsole.

3. Then start linux native mingw gdb, connect to the remove debuggee.
   x86_64-w64-mingw32-gdb then target remote localhost:3456

4. Now you can set breakpoints and print variable values:
   

After some simple configuration, you can even take the advantage of VSCode:

Maybe there are still some bugs while running gdbserver under wine, but it's enough for me to just watch the code flow.

Thanks for the information, I'm glad to see it's possible to setup VSCode debuger for DXVK. I'm looking for quick and easy solution for a long time, but was too lazy to dig into it by myself.

Now I'm on the way to replicate your experience and have some notes:

1. Looks like winedbg --gdb --no-start --port 2345 cube.exe acts similar to gdbserver

   002f:0030: create process 'Z:\tmp\vk\x32\cube.exe'/0x110bd0 @0x407df0 (0<0>)
   002f:0030: create thread I @0x407df0
   target remote localhost:2345
   

2. I able to reproduce breakpoints and local variables from your VSCode screenshot with winedbg by setting d3d11.dll as "program". But no symbols loaded for other *.dlls or exe, so I created two separate configurations for d3d11.dll and dxgi.dll, and still looking for solution to load all symbols (d3d11.dll, dxgi.dll and "launcher.exe").

So in general it's the same configuration as described in WINE wiki. Also checked with kdbg -r localhost:2345 d3d11.dll .

Ok, it's possible to load symbols with following GDB commands:

add-symbol-file  /path/to/dxgi.dll 0x6f201000
add-symbol-file  /path/to/d3d11.dll 0x6a341000

Where .text section address taken from objdump output:
$ x86_64-w64-mingw32-objdump --section-headers d3d11.dll

  0 .text         001c1208  000000006a341000  000000006a341000  00000600  2**4
                  CONTENTS, ALLOC, LOAD, READONLY, CODE, DATA

In "step-by-step" words:

1. $ winedbg --gdb --no-start --port 2345 program.exe
2. Configure debugger:
   • set port
   • add commands to load symbols
   • if "program"/"executable" set to program.exe than it's symbols also will be loaded in the first place, anyway it used only for this purpose (winedbg launching executable)
3. Set breakpoints and start debugger.

_NOTE: I think no matter which debugging information format used with this configuration if it supported by GDB. Since winedbg not used as symbols provider, but launcher.
Also -O[2,3]/-Og option causes some <optimized out> values in "local variable monitor", so I omitting it (e.g. tested w/ cpp_args = ['-gdwarf-4', '-g3', '-fvar-tracking-assignments' ]).
https://gcc.gnu.org/onlinedocs/gcc-8.1.0/gcc/Debugging-Options.html#Debugging-Options_

@Inori Did you use MoltenVK for vulkan support on macOS ? I do not know how "hacky" your winemav.drv hack is, but did you consider submitting it to wine ?

@ImperatorS79
Sorry I just see your post now.

Yeah, I'm using MoltenVK as the MacOS vulkan driver, but the code I've write is just "quick and dirty", I don't think wine team will accept it.

And besides, MoltenVK is still poor and missing many features, thus I can only run some very simple Windows vulkan programs successfully, and even the simplest d3d11 demo just gaves me black screen.