-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Compiler exceptions should be visible at default verbosity in dotnet build #21814
Comments
@jaredpar Do you think it is reasonable to aim to do this (have the compiler build task print detailed exception info when the compiler crashes) in the 15.5 timeframe? |
yes definitely. |
@jaredpar Is there something that can be set in msbuild to bump the csc.exe verbosity without bumping the entire build to /v:diag, which spews a ton of other stuff to the console? |
i was imagining no msbuild work here. Rather we just wrap our main method with try catch and print from there. |
@jaredpar I was asking something different: Is there a workaround with currently shipped bits other other than msbuild /v:normal or /v:diag? One which causes the stack trace to be dumped on compiler crash without otherwise making the entire build more verbose? |
Relates to #22332 |
Looks like this is tracking the same issue as #23743 |
Version Used: .Net Core 2.0
Steps to Reproduce:
Create a .Net Core project that causes the C# compiler to throw an exception and run
dotnet build
. For example, in .Net Core 2.0 that can be code that triggers #21645:Expected Behavior:
dotnet build
shows the exception.Actual Behavior:
The output of
dotnet build
is not very useful in diagnosing the issue:To see the exception, you have to use
dotnet build /v:n
, which also includes lots of irrelevant information:Related issue: https://github.com/dotnet/cli/issues/7556.
Originally reported as https://github.com/dotnet/cli/issues/7558.
According to @dasMulli (see https://github.com/dotnet/cli/issues/7558#issuecomment-326041206), the relevant code is in this repository.
The text was updated successfully, but these errors were encountered: