http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspxThis script automates a technique I’ve been using for a long time whenever I need to see the stack for exceptions hidden in a call stack and if you are like me, you prefer to use an automated approach rather than a manual approach. I’m not going to writeen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspx#7124437Wed, 16 Jan 2008 05:35:57 GMT91d46819-8472-40ad-a661-2c78acb4018c:7124437MSDN Blog Postings » [PowerShell Script] Displaying the Call Stack for Inner and Hidden Exceptions<p>PingBack from <a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2008/01/15/powershell-script-displaying-the-call-stack-for-inner-and-hidden-exceptions/">http://msdnrss.thecoderblogs.com/2008/01/15/powershell-script-displaying-the-call-stack-for-inner-and-hidden-exceptions/</a></p> http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspx#8355909Fri, 04 Apr 2008 10:05:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:8355909Roberto Farah<p>New version. Now it doesn't use start-sleep anymore because PowerDbg v3.0 and later doesn't require forced delays anymore!</p>http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspx#8999837Tue, 14 Oct 2008 20:37:14 GMT91d46819-8472-40ad-a661-2c78acb4018c:8999837lsalamon<p>Hi,</p> <p>About error when opening &quot;C:\Arquivos de programas\Debugging Tools for Windows x86\POWERDBG.LOG&quot; I do this :</p> <p>- desinstall &quot;Debugging Tools for Windows (x86)&quot; because </p> <p>this is installed in this path : &quot;C:\Arquivos de programas\Debugging Tools for Windows (x86)&quot;</p> <p>- reinstall in new path : &quot;&quot;C:\Arquivos de programas\Debugging Tools for Windows x86&quot;</p> <p>The new path don't have parenthesis in name, like first default installation. </p>http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspx#9002291Thu, 16 Oct 2008 23:36:46 GMT91d46819-8472-40ad-a661-2c78acb4018c:9002291Roberto Farah<p>Hi ISalamon,</p> <p>One week ago a co-worker reported the same problem. This is a bug in PowerDbg code, when handling parentesis. I&#180;d suggest the same workaround you already applied. Soon the tool is going to use a COM object to communicate with WinDbg, so hopefuly this problem will be solved. :)</p> <p>Thanks!</p> http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspx#9394444Wed, 04 Feb 2009 06:46:22 GMT91d46819-8472-40ad-a661-2c78acb4018c:9394444Debugging Toolbox<p>I’m very excited to present the new PowerDbg v5.0! There’s just one change, but it’s a HUGE change that</p> http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspx#9490821Thu, 19 Mar 2009 21:30:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:9490821Debugging Toolbox<p>So, here we go again. This is a minor version with a few new cmdlets. These new cmdlets are those that</p> http://blogs.msdn.com/debuggingtoolbox/archive/2008/01/15/powershell-script-displaying-inner-and-hidden-exceptions.aspx#9550095Wed, 15 Apr 2009 08:47:07 GMT91d46819-8472-40ad-a661-2c78acb4018c:9550095Debugging Toolbox<p>This version has two improvements and some scripts were changed to be compatible with this new version:</p>