Skip to content

Conversation

@thaystg
Copy link
Member

@thaystg thaystg commented Feb 17, 2022

Backport of #60770 and #64566 to release/6.0
Fix an assertion when trying to get the callstack from a DIM.

Customer Impact

When trying to get the callstack from a DIM was hitting an assert and stopping the process.

Testing

Automatic tests added

Risk

Low Risk.

@teo-tsirpanis teo-tsirpanis added the Servicing-consider Issue for next servicing release review label Feb 17, 2022
@teo-tsirpanis teo-tsirpanis added this to the 6.0.x milestone Feb 17, 2022
@teo-tsirpanis
Copy link
Contributor

Pardon me if I'm wrong but my understanding is that servicing PRs need to be tagged with Servicing-Consider and put on the appropriate release milestone. If that's OK I will keep that in mind for future servicing PRs I encounter.

c.c. @eiriktsarpalis

@eiriktsarpalis
Copy link
Member

@teo-tsirpanis Servicing-Consider is meant to mark a PR for director-level review, so I'd leave it up to the PR authors to apply the label themselves when they feel it's ready. I think it should be fine to leave it here though, thanks!

StringSplitOptions.None
);

//Console.WriteLine(testStack);
Copy link
Member

Choose a reason for hiding this comment

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

Forgotten commented out value check :)

@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Feb 22, 2022
@rbhanda rbhanda modified the milestones: 6.0.x, 6.0.4 Feb 22, 2022
@lewing
Copy link
Member

lewing commented Mar 10, 2022

aot failure is #66366

@ericstj ericstj merged commit 518c76f into dotnet:release/6.0 Mar 10, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Apr 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-VM-meta-mono Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants