-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Better diagnostic for collected delegate #9418
Comments
What are the MDA you are really interested in? Is the CollectedDelegateMDA the only one? |
@jkotas yes, now I'm interested in CollectedDelegateMDA because we often face this problem. But there are other assistants that can be helpful, I think. |
This diagnostic for calls on collected delegates should be on by default. There is no good reason why it needs to be a special runtime knob. @parjong started working towards it in dotnet/coreclr#12731 by introducing
Doing these two things will make it better than what you get out of the MDA. |
@jkotas thank you for suggestion! I'll try to use this approach. |
Fixed by dotnet/coreclr#15809 |
Current version of CoreCLR contains code for supporting MDAs. It is compiled and some parts of it were removed as dead. MDAs are very useful to detect application bugs that related to transitions beetween managed and unmanaged code, for example, to detect calls of collected delegates.
I've tried to enable current implementation of MDAs in coreclr (dotnet/coreclr#15464):
xmlparser
project to coreclrmda.cpp
,mdadac.cpp
, etc.)After several fixes CallbackOnCollectedDelegate MDA starts work for me:
Is it correct approach to enable MDAs or have you another plans about it?
Thank you!
The text was updated successfully, but these errors were encountered: