Wine debug in OSX

[stuta]

I have this launch file and it starts the debugger and stops at breakpoints.

The trouble is that when it stops at the breakpoint it does not show where it stopped and it does not show variables. I tried with VSCode Insiders and the latest stable versions.

I tried with "communication": "pipe" and without pullBreakpointsSupport but they did not affect it, it worked the same way with or without both options.

{
  "name": "lj current wine",
  "type": "lua-local",
  "request": "launch",
  "pullBreakpointsSupport": true,
  "cwd": "${fileDirname}",
  "program": {
    "command": "wine64"
  },
  "args": ["~/nc/bin/bin_win_x64/lj.exe", "-e", "'require([[lldebugger]]).runFile([[${file}]],true)'"]
}

[Ismoh]

Anyone out here with OSX?
I only have Windows10 + WSL.

[stuta]

Anyone out here with OSX? I only have Windows10 + WSL.

Well... me. Send me debug instructions.

[sewbacca]

I don't have OSX either, however, this looks like the debugger can't find the file.

Have you tried adding the folder to the scripts roots?

"scriptRoots": [
     "${fileDirname}",
],

Though I would not expect it to stop at a breakpoint, if it doesn't know where it is.

Another thing that comes to mind is that the paths in wine64 might be different, than on your host system. If the above doesn't fixes it, could you run a file, where the debug breakpoints won't trigger correctly and print out the following line?

print(debug.traceback())

[sewbacca]

In addition, have you tried running your file via tomblinds original version? Does the issue occur there too?

[stuta]

In addition, have you tried running your file via tomblinds original version? Does the issue occur there too?

I'm quite sure it worked about a year ago in the original version, but lots of programs have been changed (like wine) and it did not work anymore with the original version.

The debugger does stop in breakpoints correctly, but vscode does not show where the breakpoints are and the variables are not shown when stopped.

[Ismoh]

In addition you can have a look into the extension logs:
https://stackoverflow.com/a/54381900/3493998
Maybe there is a more precise hint or error.

[stuta]

I tried scriptRoots, no change.

The first error comes when I start debugging and it stops at the breakpoint. The second error comes when I stop debugging.

[Ismoh]

In addition, have you tried running your file via tomblinds original version? Does the issue occur there too?

I'm quite sure it worked about a year ago in the original version, but lots of programs have been changed (like wine) and it did not work anymore with the original version.

The debugger does stop in breakpoints correctly, but vscode does not show where the breakpoints are and the variables are not shown when stopped.

There were dependency changes on this repo. Especially on vscode dependencies: for one example. Might this be a reason? Were there changes on vscode regarding wine?
vscode-debug-adapter-protocol, but I can't see any wine related stuff on first glance

[Ismoh]

This looks kinda promising, @stuta:
microsoft/vscode#196948

[Ismoh]

any news on this @stuta ?