You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on the DAP for PHP (https://github.com/xdebug/vscode-php-debug/) and while testing an unusual setup scenario I came to a problem that I'm not sure how to properly solve.
It's regarding path format in the Source type part of StackTraceReqeust and others.
The setup that I had - this is because I did some debugging - was my IDE (neovim) was running in WSL (posix), the debuggee (php) was also running in WSL (posix) but the DAP was running on Win32 (within a VSCode debug session).
The problem that I faced was the code of DAP manipulates paths using https://www.npmjs.com/package/path that by default uses path format depending on the platform it runs on. I can also explicitly tell the library to either use posix or win32 format but the DAP has, as far as I can tell, no idea what platform the client (IDE) is running on.
I understand this is a veeeery specific corner case and probably irrelevant in real life, but I wanted to see if somebody else thinks this should somehow be covered either by a field in InitializeRequestArguments.
After searching around bit more I found some related issues (microsoft/vscode-debugadapter-node#3) and the pathFormat and DebugSession.setDebuggerPathFormat but none of those seem to solve this on the protocol level. Question remains, how does the DAP know if the IDE is running POSIX or WIN32.
Activity
zobo commentedon Mar 15, 2021
After searching around bit more I found some related issues (microsoft/vscode-debugadapter-node#3) and the
pathFormatandDebugSession.setDebuggerPathFormatbut none of those seem to solve this on the protocol level. Question remains, how does the DAP know if the IDE is running POSIX or WIN32.fix: clarify expectations around source.path format
connor4312 commentedon Dec 18, 2025
Thanks for the issue, I opened #581 to try to clarify it. Please let me know what you think!
fix: clarify expectations around source.path format (microsoft#581)