Stack Traces

Tuesday, May 13, 2003

Just when you think you know all the cool stuff the framework does, something like System.Diagnostics.StackTrace pops up. Try this:

catch(Exception ex)
{
StackTrace st = new StackTrace(ex, true);
}

Now, you have a strongly typed version of the stack trace from your exception. Very cool stuff, you can get IL offsets, native byte offsets, source code files, line numbers, column numbers, etc. You can also use the StackTrace class to get a stack trace from any arbitratry line of your code.

I wonder how much more hidden goodness is out there...

4 Comments

Can you get line #s on a 'release' build?

M. Keith Warren - Tuesday, May 13, 2003 12:04:00 PM

Not unless you include the PDB info, but that is generally what seperates a release from a debug build :-). You can still get the IL offset though, which can be used to locate the line of code that caused the error.

Jesse Ezell - Tuesday, May 13, 2003 12:10:00 PM

"I wonder how much more hidden goodness is out there..."

Lots, no doubt :)

Tim Marman - Tuesday, May 13, 2003 1:52:00 PM

You can sometimes get the IL offsets. Unfortunatly in a lot of JITed code they're lost. BTW, if you use NUnitAddin you can do...

catch(Exception ex) { Debug.WriteLine(ex, "_il") } I'll let you find out what it does... ;)

Jamie Cansdale - Tuesday, May 13, 2003 3:21:00 PM

Comments have been disabled for this content.