-
Notifications
You must be signed in to change notification settings - Fork 111
DeveloperExceptionPage does not show line numbers in stack trace #372
Comments
-_- This has been regressed so many times. We seriously need to have end-to-end functional tests validating this. |
Well, apparently this is a known issue: aspnet/Mvc#6120. |
Investigated this guy. Looks like there's a core clr issue with StackFrame that broke from netcoreapp1.1 => netcoreapp2.0. Filed an issue here. Could use an external label 😄 |
We can keep this issue here at least to track. |
@Eilon we keep this in preview1 or move out? (and close if CoreCLR issue gets fixed) |
Can keep it here for now until we at least find out what the conclusion is on the .NET side. |
This should now be fixed in CoreFX with dotnet/corefx#19364. |
@lt72 thanks! |
@NTaylorMullen - can you confirm we're seeing the right thing on the latest build of the CLI that I sent out? |
Can you unskip aspnet/Mvc#6120? |
This issue resurfaced again in the mirror, probably because the corefx team merged their commits from preview1(where it regressed) to dev(where it was working when @NTaylorMullen unskipped this). |
This has been fixed. https://github.com/dotnet/corefx/issues/19838 |
This has been regressed again for net461 apps. Re-opened the corefx issue: https://github.com/dotnet/corefx/issues/19838 |
Do we need to revive this - dotnet/extensions@31a4622? |
Yup, opened this issue. To work around this issue for those watching you can add this to your csproj: <DebugType Condition="'$(TargetFrameworkIdentifier)'=='.NETFramework'">Full</DebugType> |
Have other issues tracking the fix of this for net461 now: |
Using 2.0.0-preview1 bits:
Throw a runtime exception during request processing, e.g. in an inline middleware, in a Controller action, in a Razor view/page, and the exception page displays but the stack trace contains no line numbers:
The text was updated successfully, but these errors were encountered: