Add generate crash report flag (and other flags) to WriteDump diagnostics IPC message #60775
Assignees
Labels
area-Diagnostics-coreclr
enhancement
Product code improvement that does NOT require public API changes/additions
Milestone
Comments
dotnet-issue-labeler
bot
added
the
untriaged
|
Tagging subscribers to this area: @tommcdon Issue DetailsBackground and MotivationThe VS for Mac team needs a way to generate the crash report json file for hangs. Proposed FeatureAdd a flags argument to the Microsoft.Diagnostics.NETCore.Client.WriteDump/WriteDumpAsync API that enables crash report json and other logging options (verbose and log to file). Also see issue: dotnet/diagnostics#2698
|
noahfalk
added
the
enhancement
|
I just commented on dotnet/diagnostics#2698. |
mikem8361
added a commit
to mikem8361/runtime
that referenced
this issue
Oct 28, 2021
crash report flag to be passed through to createdump for VS4Mac. Issue: dotnet#60775
mikem8361
added a commit
that referenced
this issue
Nov 1, 2021
Fix dump generation issues for VS4Mac Fixes issue: #60932 Fix how the load bias is calculate for shared modules Add new generate core dump IPC command that allows the generate crash report flag to be passed through to createdump for VS4Mac. Issue: #60775 VS4Mac needs to distinguish between WriteDump/no signal and unknown signal ExceptionType Change unknown signal exception type to 0
mikem8361
added a commit
to mikem8361/runtime
that referenced
this issue
Nov 1, 2021
The VS4Mac team found two issues preventing them from successfully diagnosing VS4Mac failures on .NET: 1) Multiple "crashed" threads in the crash report json (dotnet#60932). 2) No flag or way to generate the crash report for hangs via the diagnostic server IPC commands (dotnet#60775). Add new generate core dump IPC command that allows the generate crash report flag to be passed through to createdump for VS4Mac. VS4Mac needs to distinguish between WriteDump/no signal and unknown signal ExceptionType. Change unknown signal exception type to 0. Issue: dotnet#60775 Fix how the load bias is calculate for shared modules Local testing with the SOS tests. VS4Mac team testing and verification. Low risk because it only affects createdump, dump IPC command and the runtime dump generation path.
Anipik
pushed a commit
that referenced
this issue
Nov 9, 2021
The VS4Mac team found two issues preventing them from successfully diagnosing VS4Mac failures on .NET: 1) Multiple "crashed" threads in the crash report json (#60932). 2) No flag or way to generate the crash report for hangs via the diagnostic server IPC commands (#60775). Add new generate core dump IPC command that allows the generate crash report flag to be passed through to createdump for VS4Mac. VS4Mac needs to distinguish between WriteDump/no signal and unknown signal ExceptionType. Change unknown signal exception type to 0. Issue: #60775 Fix how the load bias is calculate for shared modules Local testing with the SOS tests. VS4Mac team testing and verification. Low risk because it only affects createdump, dump IPC command and the runtime dump generation path.
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Background and Motivation
The VS for Mac team needs a way to generate the crash report json file for hangs.
Proposed Feature
Add a flags argument to the Microsoft.Diagnostics.NETCore.Client.WriteDump/WriteDumpAsync API that enables crash report json and other logging options (verbose and log to file).
Also see issue: dotnet/diagnostics#2698
The text was updated successfully, but these errors were encountered: