since pre .net 4.5 runtimes (including sl/wp) not async-aware, stack traces generate show compiler-generated class/method names (like d_15
).
does know of utility generate better stack trace given runtime stacktrace, assembly , pdb?
to clear: i'm not looking complete async stack, better view of method threw exception
it seems above statement not clear enough, here example:
public async void foo() { await bar(); } public async task bar() { async somethingtomakethismethodasync(); throw new exception() }
when exception thrown bar
, stacktrace contain generated method names (d_15()
). i don't care foo called bar. want know bar method threw exception
andrew stasyuk has great article in msdn magazine http://msdn.microsoft.com/en-us/magazine/jj891052.aspx details async causality chains way aid in debugging in light of disjoint , confusing stack traces.
Comments
Post a Comment