http://blogs.msdn.com/b/shawnfa/archive/2005/01/19/356376.aspxMike's got an interesting piece up today about using WinDbg to find the actual call stack of an unmanaged (or managed for that matter) exception . It's this kind of power debugging technique that makes WinDbg my all time favorite debugger.en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/shawnfa/archive/2005/01/19/356376.aspx#356421Wed, 19 Jan 2005 23:16:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:356421Mike StallThe VS guys pointed out that you can do this in Visual Studio too (I didn't realize at the time I posted). See <a target="_new" href="http://blogs.msdn.com/jmstall/archive/2005/01/18/355697.aspx#356316">http://blogs.msdn.com/jmstall/archive/2005/01/18/355697.aspx#356316</a> <br><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=356421" width="1" height="1">