-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode protocol "launch" command "sourceFileMap" option support. #78
Comments
We don't support this for sure. Could you please share more info about source file mapping through the VSCode protocol? Do you mean "Source Request" https://microsoft.github.io/debug-adapter-protocol/specification? |
Apologies, turns out its not something that the VSCode protocol manages, but rather is a feature of the debugger. I believe debugger engines like When testing with vsdbg it comes through with the "attach" or "launch" command in the argument list like so Then presumably the debugger behind the scenes will replace any instance of Curious what it would take to add that flexibility to netcoredbg 🤔 |
I see, you mean https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md#source-file-map, we already support "justMyCode" and "enableStepFiltering" launch options, so, add more launch options possible. Unfortunately, we don't have time right now, but I added this to feature requests list. |
Yes! That's great, I appreciate it. In the meantime I found a less flexible work around that can be set during build. By using property EX. I am building in
Both of these will map the file locations in the pdbs to |
Question for you guys,
Does
netcoredbg
support source file mapping through the VSCodeProtocol? Just looking through vscodeprotocol.cpp, I don't believe it does but I could be missing something.Thank you!
The text was updated successfully, but these errors were encountered: