-
Notifications
You must be signed in to change notification settings - Fork 122
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
Can sourcelink support debugging through internal code and abstract implementations? #1221
Comments
Never mind, I had "Enable Just My Code" on in VS, without that debugging into those code paths kinda works. F12 into Although the code is in the same library: |
This seems more a debugger issue. Source Link lets the debugger know how to download the source files referenced by the PDB, but it does not comment on how the debugger should parse the files. For that, the debugger should use the other information in the portable PDB. I get the impression that, if the debugger supports the programming language of the source files, then it could use the PDB for F12 to find the source code of a method definition:
However, F12 finding the source code of a type definition looks harder, because types do not have sequence points, and the specification of the CustomDebugInformation table doesn't mention anything that could be used for navigating from a TypeDef to a Document. |
Is there a way to enable/support debugging and stepping through internal code in sourcelink?
As an example, the actual implementation of the shared array pool is in an internal class.
F12 into
SharedArrayPool
does nothing though.Debugging and stepping into
ArrayPool<byte>.Shared.Rent(1000);
also does not work and the debugger just steps overRent(..)
as this is an abstract method.Thanks
The text was updated successfully, but these errors were encountered: