-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[release/8.0] Don't shut down event pipe in DLLs on Windows #92044
Conversation
This reverts commit e811599.
Works around #89346.
…e.Publish.targets Co-authored-by: Elinor Fung <[email protected]>
…e.Publish.targets Co-authored-by: Andy Gocke <[email protected]>
…e.Publish.targets
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsBackport of #91715 to release/8.0 Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved. this can be merged when ready
Backport of #91715 to release/8.0
/cc @MichalStrehovsky
Customer Impact
Trying to enable
EventSourceSupport
in a shared library project on Native AOT currently results in a build failure since this is actively blocked in the targets. ButEventSourceSupport
/event pipe mostly work, with some issues (#91762).The blocking makes it impossible for anyone to run diagnostics on their shared library. This is a regression from .NET 7, where it was at least possible to get GC ETW events in PerfView on Windows.
This changes the blocking to a suppressible warning, and fixes and issue that was causing a shutdown hang.
Testing
Manual test of dotnet trace with a shared library.
Risk
EventSourceSupport
is opt in. This change allows a scenario (with a warning) that was previously forbidden. It should not affect any other codepaths. The risk is low.IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.