Skip to content
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

Increase CoreCLR dump information #49790

Merged
1 commit merged into from
Dec 4, 2020
Merged

Increase CoreCLR dump information #49790

1 commit merged into from
Dec 4, 2020

Conversation

jaredpar
Copy link
Member

@jaredpar jaredpar commented Dec 4, 2020

This sets environment variables that will help make the dumps for a CLR
bug more actionable by the runtime team.

dotnet/runtime#45557

This sets environment variables that will help make the dumps for a CLR
bug more actionable by the runtime team.

dotnet/runtime#45557
@jaredpar
Copy link
Member Author

jaredpar commented Dec 4, 2020

@tmat, @dotnet/roslyn-infrastructure PTAL

This is to help the runtime team track down the cause of dotnet/runtime#45557

@jaredpar jaredpar requested a review from a team as a code owner December 4, 2020 17:08
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approval

@ghost ghost merged commit 8fb010e into dotnet:master Dec 4, 2020
@ghost ghost added this to the Next milestone Dec 4, 2020
#if NETCOREAPP
// These environment variables will generate better dump information for the runtime team
// that will help them track down a GC issue that is impacting ConcurrentDictionary
// https://github.com/dotnet/runtime/issues/45557
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for linking to the bug!

@jaredpar jaredpar deleted the env branch December 4, 2020 19:05

void MaybeAddStressEnvironmentVariables()
{
#if NETCOREAPP
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It just occurred to me that RunTests.dll itself always defines this symbol even if we are running net472 tests. May be more appropriate to check for the absence of "net472" in Options.TargetFrameworks

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doh! You're right I missed that. I will get that fixed up in a bit.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants