-
Notifications
You must be signed in to change notification settings - Fork 127
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
Linking out of debugging support for .NET5 #1093
Comments
StackFrame tracking at dotnet/runtime#34910 |
There is a similar story with types that are only necessary for COM. See dotnet/runtime#36659. For both COM and debugging, we are "rooting" specific types in the libraries. For debugging we have:
We could use the same mechanism to preserve and trim these types based on a "feature switch" that is respected in the descriptor XML files. |
@eerhardt could you please look into annotating the debugger dependencies in libraries with correct feature tag. I also think as part of this job we need to figure out how to move SPC XML descriptor to src/libraries |
) * Remove debug only attributes when Debugger.IsSupported is false. Contributes to dotnet/linker#1093 * Move debug only attributes to shared CoreLib.
I believe this issue was addressed for .NET 5. Can it be closed? (I don't have permission to close it) |
There is still unconditional code in libraries for debugger support but I agree it can be closed for linker |
Do you happen to have an example? I was under the assumption we got all of them. |
Nothing major, mostly stuff like stubbing out the whole System.Diagnostics.Debugger type or conditions like https://github.com/dotnet/runtime/blob/6072e4d3a7a2a1493f514cdf4be75a3d56580e84/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/TaskFactory.cs#L1591 |
For .NET5 it would be better to have MSBuild property which controls the debugging support as a complete feature. This would cover the following behavior inside linker.
This property could be set automatically when
'$(DebugType)'=='none'
.The text was updated successfully, but these errors were encountered: