dotnet/msbuild

Last-chance exception handling could indicate how it was called

Open

#1,043 opened on Sep 19, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (1,364 forks)batch import
Area: Debuggabilityhelp wantedtriaged

Repository metrics

Stars
 (5,062 stars)
PR merge metrics
 (Avg merge 11d 7h) (125 merged PRs in 30d)

Description

There are many codepaths that can get to DumpExceptionToFile, which is a last-ditch effort to try to preserve some debugging information in the case of bad failures. It'd be great if it was easy to identify which path was used for a given exception dump. Knowing, for example, that this exception was caught by the AppDomain's UnhandledException handler versus an explicit catch somewhere could be useful information.

Contributor guide

Research direction
Identify all call sites of DumpExceptionToFile and modify the method to accept a context parameter. Update each call site to pass an appropriate identifier.
Tech stack
csharp
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NETGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75