Consider this small program. Ignore, if you will, the generic catch, I've kept it brief to try and illustrate the point:
private static void Main(string[] args)
{
Try(Fail);
}
private static void Fail()
{
var x = ((string)null).Clone();
}
private static void Try(Action action)
{
try
{
action();
}
catch (Exception exc)
{
Debug.WriteLine(exc.StackTrace);
}
}
When run, the following (with some of the path info removed) is produced:
at Scratch.Program.Fail() in Program.cs:line 27
at Scratch.Program.Try(Action action) in Program.cs:line 34
My question is - why does the stack trace of the exception stop unwinding the method chain at the Try()
method? I would expect it to unwind past that to the Main()
method.
I haven't been able to find any documentation about what it is that stops exception unwinding going past the Try()
- so I'd like to understand this.
This:
catches your exception inside
Try
, and doesn't propagate upwards to unwind the callstack, it simply swallows the exception. Therefor, you don't seeMain
as part of your stacktrace. If you want to seeMain
, leave thecatch
to yourMain
method:And now you see:
Exception.Stacktrace
callsGetStackTrace
which in the end will callnew StackTrace(this /* exception object */, true)
. When used with these parameters the stack trace will be evaluated for the point of the exception until the current method. You can check that yourself when addingThe second version is the stacktrace returned by
exc.StackTrace
, the first is the full stacktrace from the current method to the entry point or thread start.