[release/7.0-staging] Store entry assembly path for easy access for diagnostics#95047
Conversation
- Add `g_EntryAssemblyPath` global variable holding the full path to the entry assembly - Set right before loading the entry assembly (so also before startup hooks are run) - NULL if there is no entry assembly - Ensure value is included dumps - For triage dumps, the dumped value is updated to only be the assembly file name instead of the full path
ghost
added
the
elinor-fung
changed the title
|
/backport to release/6.0-staging |
|
Started backporting to release/6.0-staging: https://github.com/dotnet/runtime/actions/runs/6938665661 |
jeffschwMSFT
left a comment
jeffschwMSFT
left a comment
There was a problem hiding this comment.
approved. we will take for consideration in 7.0.x
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsBackport of #95045 to release/7.0-staging /cc @elinor-fung Customer ImpactThe entry assembly is currently not exposed in a way that is easy to access for diagnostics - for example, crash dumps. This means that for an application started via the dotnet executable ( See #94474 TestingManual validation. RiskLow IMPORTANT: If this backport is for a servicing release, please verify that:
|
5 participants
Backport of #95045 to release/7.0-staging
/cc @elinor-fung
Customer Impact
The entry assembly is currently not exposed in a way that is easy to access for diagnostics - for example, crash dumps. This means that for an application started via the dotnet executable (
dotnet app.dll), there isn't a good way to determine the managed assembly from a dump - particularly so for a non-heap dump.See #94474
Testing
Manual validation.
Risk
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.