When you get an Exception traced in Indigo, part of that trace includes the callstack which is naturally traced as part of Exception.ToString(). However, callstack information is generally useful for other non-Exception traces (for example, trying to track down who is Aborting a socket). Part of the beauty of our tracing infrastructure is that it’s really easy to modify your trace listener. It turns out there is a built-in option for emitting callstacks. Simply add:

to your listener config.

The relevant line of config then looks like:

<add name="multifile"
     type="System.Diagnostics.XmlWriterTraceListener"
     traceOutputOptions="Callstack"
     initializeData=".Whatever.xml" />

Happy debugging!