1

C# exception stack traces sometimes have line numbers that don't match the line numbers in the IDE (e.g. 1, 2).
Can I make the line numbers accurate, without harming performance too much?
My codebase is in .net core 3.1 & .net 6.

I've seen previous discussions of this on stack overflow, however it's eighter outdated (from before .net core) or doesn't propose general solutions.

Gal A.
  • 172
  • 1
  • 13

1 Answers1

2

Use Debug mode, Release mode optimization may cause this wrong tracing.

Disable Optimization in Configuration:

In your project settings, make sure that you are compiling in Debug mode while developing. Debug builds usually contain more accurate debugging information. In Release mode, compilers apply various optimizations that can make line numbers less precise.

But if you insist on using Release i guess

Use PDB Symbol Files:

Ensure that your project generates PDB (Program Database) symbol files. PDB files contain debugging information that allows the debugger to map machine code back to source code lines more accurately.

Avoid Inlining and Compiler Optimizations:

Some code optimizations like inlining can make it difficult for the debugger to accurately trace the execution path. You can use the [MethodImpl(MethodImplOptions.NoInlining)] attribute on methods that you want to avoid inlining. As described here

Update to at least .NET 6:

.NET 6 has improvements in debugging and performance, so consider upgrading all project to a >=6 version to see if it resolves your issue.

Adjust Debugging Settings in IDE:

Check your IDE's settings. In Visual Studio check "Suppress JIT optimization on module load." This can help with accurate debugging.

Andi
  • 71
  • 4
  • 1
    Thanks alot for the detailed answer :). This issue happens on .net 6 with pdb files. I want accurate errors in production, so the tips on the IDE and compiling on debug don't seem relevant. Putting an attribute on every method is also not feasible. – Gal A. Aug 21 '23 at 14:33