-
Notifications
You must be signed in to change notification settings - Fork 37
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
Ensure source links work #156
Comments
I found that the following sequence of commands can be used to show the source links embedded in the PDB.
This outputs something like
I found pdbdump.exe on the \vcfs\builds\msvc\main\20221214.01\binaries.amd64ret\bin\amd64 release share (path probably needs to be adjusted for current releases).
I found pdbstr.exe in d:\nugetcache\microsoft.windows.dbg.srcsrv.10.0.17074.10021\lib\amd64 The output file generated by the above command (d:\temp\out.txt) shows the JSON sourcelink map:
It seems that the local paths in the above map contain a mix of '\' and '\\' path separators. I'm guessing that in order to be valid JSON, all local path separators should be '\\'. |
Co-authored-by: tudorm <[email protected]>
Replacing VSO:5259293 in an effort to create bugs that are more specific and further upstream.
Among the things that VSO:5259293 asked for was for V8 source code to resolve in the debugger. As I understand it, we attempted to address this by the addition of source links (scripts\fetch_code.ps1). However, as per a quick check with a devinstalled Office (
lkg/main/dev 16.0.16012.15010 (b7ab2e58b0)), symbols get loaded ...
However, sources do not appear to get resolved (using v8runtime::V8Runtime::ExecuteString as an example, WinDbg does not open any source file):
The text was updated successfully, but these errors were encountered: