<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Defrag Tools: #14 - WinDbg - SOS</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS/RSS"></atom:link>
	<image>
		<url>http://media.ch9.ms/ch9/f9f0/c1047a76-2158-4998-803f-2c2db849f9f0/DefragTools14_220.jpg</url>
		<title>Channel 9 - Defrag Tools: #14 - WinDbg - SOS</title>
		<link></link>
	</image>
	<description>In this episode of Defrag Tools, Andrew Richards and Larry Larsen continue looking at the Debugging Tools for Windows (in particular WinDbg). WinDbg is a debugger that supports user mode debugging of a process, or kernel mode debugging of a computer. This installment shows how you can view the user mode call stack and stack variables in a native, managed (.NET) or Silverlight process. We&amp;nbsp;use these commands: dv dt !sos.dumpstack !sos.dumpstackobjects / !sos.dso !sos.dumpobj / !sos.do !sos.printexception / !sos.pe .frame .f&amp;#43; .f- .load .unload .loadby .chain lm / lmm / lmvm .extmatch .prefer_dml 1 .lines .ecxr .cls Make sure you watch Defrag Tools Episode #1 for instructions on how to get the Debugging Tools for Windows and how to set&amp;nbsp;the required environment variables for symbols and source code resolution. Resources:Microsoft Windows SDK for Windows 7 and .NET Framework 4Sysinternals ProcDumpSilverlight Developer Runtime Timeline:[01:05] - Native vs. Managed variables[02:35] - Display Variables (dv) and Display Type (dt)[03:38] - Debugger Extensions (.chain, .load, .unload)[05:43] - Extension Match (.extmatch)[07:08] - ProcDump v5.1 captures a .NET 2 and .NET 4 exception[08:46] - .NET engines versus .NET releases[10:34] - Loading &amp;quot;Son of Strike&amp;quot; for .NET 2 engine applications (.loadby sos.dll mscorwks)[13:44] - Loading &amp;quot;Son of Strike&amp;quot; for .NET 4 engine applications (.loadby sos.dll clr)[15:24] - Dump Call Stack (!sos.dumpstack)[16:32] - Dump Stack Objects (!sos.dumpstackobjects / !sos.dso)[17:30] - Dump Object (!sos.dumpobject / !sos.do)[17:51] - Enable DML (.prefer_dml 1)[20:14] - Toggling Line display (.lines)[20:52] - Current Frame Context (.frame, .f&amp;#43;, .f-); Note, registers do not change[22:58] - ProcDump v5.1 misses Silverlight exceptions[24:50] - Silverlight Developer Runtime (dbgshim.dll &amp;amp; sos.dll)[26:10] - ProcDump v5.1 captures a Silverlight exception[28:10] - Loading &amp;quot;Son of Strike&amp;quot; for Silverlight applications (.loadby sos.dll coreclr)[30:47] - Missed: Exceptions can also be displayed with !sos.printexception / !sos.pe[31:29] -&amp;nbsp;Episode review and next week... Kernel debugging </description>
	<link></link>
	<language>en</language>
	<pubDate>Wed, 22 May 2013 09:50:46 GMT</pubDate>
	<lastBuildDate>Wed, 22 May 2013 09:50:46 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>Hi Very Nice Show <img src='http://ecn.channel9.msdn.com/o9/content/images/emoticons/emotion-2.gif?v=c9' alt='Big Smile' /> , But why Andrew is still using Windows 7</p><p>posted by Shayan_Anique</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883427608835042</link>
		<pubDate>Mon, 12 Nov 2012 18:46:00 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883427608835042</guid>
		<dc:creator>Shayan_Anique</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883427608835042">Shayan_Anique</a>: It was taped pre-GA (3rd Oct).&nbsp; My laptop is now Windows 8.</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883449054679653</link>
		<pubDate>Mon, 12 Nov 2012 19:21:45 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883449054679653</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>I'm using the PSScor DLLs instaed of SOS.</p><p><strong><a href="http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#time=31m29s">[31:29]</a> -&nbsp;Episode review and next week... Kernel debugging</strong></p><p><span>can you show ho to debug manual crash dump (<a href="http://msdn.microsoft.com/en-us/library/windows/hardware/ff545499%28v=vs.85%29.aspx">http&#58;&#47;&#47;msdn.microsoft.com&#47;en-us&#47;library&#47;windows&#47;hardware&#47;ff545499&#37;28v&#61;vs.85&#37;29.aspx</a>) when the PC freezes?<br></span></p><p>posted by MagicAndre1981</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883473957720451</link>
		<pubDate>Mon, 12 Nov 2012 20:03:15 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883473957720451</guid>
		<dc:creator>MagicAndre1981</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[http&#58;&#47;&#47;technet.microsoft.com&#47;en-us&#47;sysinternals&#47;bb842062<br><br>still has 17th october files &#63;<p>posted by Philip Saunders</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883483737082222</link>
		<pubDate>Mon, 12 Nov 2012 20:19:33 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883483737082222</guid>
		<dc:creator>Philip Saunders</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883473957720451">MagicAndre1981</a>: I didn't want to mention PSSCORx as it is a download, and not in the box.&nbsp; The vast majority of debugs don't need it (over SOS). Saying that, I did use it for the last few years up until recently where some bugs in&nbsp;them made me go back to SOS. If you like PSSCOR, also check out SOSEx, which is a companion to SOS or PSSCORx.</p><p>Kernel - I think Chad mentions <strong>CtrlScrollScroll</strong> and <strong>CrashOnNMI</strong> in next week's episode, and I think I might have in #1 too... If it was missed, email the show (<a href="mailto:defragtools@microsoft.com">defragtools@microsoft.com</a>) and I'll go over them in the next kernel debugging video shoot.</p><p>If you question is more about kernel hang debugging vs. crash debugging, we'll cover that ~6 episodes from now.</p><p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883483737082222">Philip Saunders</a>: <strong>ProcDump v5.1</strong> is still going through the signing process. I'll ping Mark to see if it can be expedited.</p><p><strong>[UPDATE: 16th Nov. 2012 -- <span>ProcDump v5.1</span> is now available]</strong></p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634884244360676898</link>
		<pubDate>Tue, 13 Nov 2012 17:27:16 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634884244360676898</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p></p><blockquote><div class="quoteText"><p></p><p><a href="/Niners/windev">windev</a> wrote</p><p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634883473957720451">MagicAndre1981</a>: </p><p>Kernel - I think Chad mentions <strong>CtrlScrollScroll</strong> and <strong>CrashOnNMI</strong> in next week's episode, and I think I might have in #1 too... If it was missed, email the show (<a href="mailto:defragtools@microsoft.com">defragtools@microsoft.com</a>) and I'll go over them in the next kernel debugging video shoot.</p><p>If you question is more about kernel hang debugging vs. crash debugging, we'll cover that ~6 episodes from now.</p><p></p></div></blockquote><p></p><p>I think you mentioned it in a show where you've explained IRQLs.</p><p>I really think it is nice to have a full step through a hang dump of the kernel. I really want to know how to start doing this.</p><p>posted by MagicAndre1981</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634884923646911920</link>
		<pubDate>Wed, 14 Nov 2012 12:19:24 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634884923646911920</guid>
		<dc:creator>MagicAndre1981</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634884923646911920">MagicAndre1981</a>: That is definitely a planned series of episodes. We will do that for user and kernel..</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885040962424051</link>
		<pubDate>Wed, 14 Nov 2012 15:34:56 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885040962424051</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p></p><blockquote><div class="quoteText"><p></p><p><a href="/Niners/windev">windev</a> wrote</p><p>We will do that for user and kernel..</p><p></p></div></blockquote><p></p><p>great <img src='http://ecn.channel9.msdn.com/o9/content/images/emoticons/emotion-1.gif?v=c9' alt='Smiley' /> You should do examples of hanging (... is not responding) Explorer and Internet Explorer.</p><p><img src="http://pureinfotech.com/wp-content/uploads/2010/11/win7-not-responding.png" alt=""></p><p>posted by MagicAndre1981</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885065416300501</link>
		<pubDate>Wed, 14 Nov 2012 16:15:41 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885065416300501</guid>
		<dc:creator>MagicAndre1981</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>My biggest complaint about this series is you can only give it 5 stars...</p><p>posted by BrianHartung</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885101980492129</link>
		<pubDate>Wed, 14 Nov 2012 17:16:38 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885101980492129</guid>
		<dc:creator>BrianHartung</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[Hey Andrew - I am trying to dig to an application crash for a third party program.  When I type lmm I see the clr module &#40;which makes sense because Event Viewer list the crash as a .NET 4 Runtime error&#41;, so I load the .NET 4 sos.dll.  But when I run the &#33;dso command I am getting &#34;Error requesting details - Unable to determine bounds of the gc heap&#34;  Any ideas&#63;  It is a mini dump and not a full one if that matters.<br><br>Also, what is the difference between &#33;clrstack and &#33;dumpstack&#63;<p>posted by Cyberbrad</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885130502813961</link>
		<pubDate>Wed, 14 Nov 2012 18:04:10 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885130502813961</guid>
		<dc:creator>Cyberbrad</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>For those looking for an easy approach to using &quot;loadby&quot; without needing to know what version of .NET you are working with, you could use a script found here:</p><p><a href="http://naveensrinivasan.com/2010/07/26/script-to-load-sos-within-windbg-based-on-net-framework-version/">http://naveensrinivasan.com/2010/07/26/script-to-load-sos-within-windbg-based-on-net-framework-version/</a></p><p>The script in question is:</p><p>!for_each_module .if(($sicmp( &quot;@#ModuleName&quot; , &quot;mscorwks&quot;) = 0) ) {.loadby sos mscorwks} .elsif ($sicmp( &quot;@#ModuleName&quot; , &quot;clr&quot;) = 0) {.loadby sos clr}</p><p>It probably would be best to have this saved to disk and just load it in the debugger, but I simply coppy and past from commonly used list of commands / scripts.</p><p>posted by DakotaGeek</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885938999842328</link>
		<pubDate>Thu, 15 Nov 2012 16:31:39 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885938999842328</guid>
		<dc:creator>DakotaGeek</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885130502813961">Cyberbrad</a>: You have to have a full dump for any managed application. Annoying - I know... especially when the application has 24Gb&#43; of RAM (eg. Exchange).</p><p>!clrstack just lists the managed frames. !dumpstack lists the managed and native frames (it's the closest to 'k').</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634886006176506245</link>
		<pubDate>Thu, 15 Nov 2012 18:23:37 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634886006176506245</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634885938999842328">DakotaGeek</a>: Here's the (abridged) code I have in my 'preferences' extension that&nbsp;does the same thing as your script. I load my extension on the command line with &quot;-a myext.dll&quot; and auto-load SOS in DebugExtensionInitialize (or manually via !loadsos). (In my version, it also executes .prefer_dml 1, etc.)</p><p><pre class="brush: cpp">
HRESULT Execute(IDebugClient* pDebugClient, PCSTR szCommand, BOOL bPrivate)
{
    HRESULT hr = E_FAIL;
    // Make our own client
    IDebugClient* pDebugCreated;
    if (SUCCEEDED(hr = pDebugClient-&gt;CreateClient(&amp;pDebugCreated)))
    {
        IDebugControl* pDebugControl;
        if (SUCCEEDED(hr = pDebugCreated-&gt;QueryInterface(__uuidof(IDebugControl), (void **)&amp;pDebugControl)))
        {
            if (bPrivate)
            {
                hr = pDebugControl-&gt;Execute(DEBUG_OUTCTL_THIS_CLIENT | DEBUG_OUTCTL_NOT_LOGGED, szCommand, DEBUG_EXECUTE_NOT_LOGGED | DEBUG_EXECUTE_NO_REPEAT);
            }
            else
            {
                hr = pDebugControl-&gt;Execute(DEBUG_OUTCTL_ALL_CLIENTS, szCommand, DEBUG_EXECUTE_NO_REPEAT);
            }
            pDebugControl-&gt;Release();
        }
        pDebugCreated-&gt;Release();
    }
    return hr;
}

HRESULT loadsos(IDebugClient* pDebugClient, PCSTR args)
{
    UNREFERENCED_PARAMETER(args);
    HRESULT hr = S_OK;
    IDebugSymbols* pDebugSymbols;
    hr = pDebugClient-&gt;QueryInterface(__uuidof(IDebugSymbols), (void **)&amp;pDebugSymbols);
    if (SUCCEEDED(hr))
    {
        ULONG nIndex = 0xFFFF;

        // .NET 2.0
        hr = pDebugSymbols-&gt;GetModuleByModuleName(&quot;mscorwks&quot;, 0, &amp;nIndex, NULL);
        if ((hr == S_OK) &amp;&amp; (nIndex !=0xFFFF))
        {
            hr = Execute(pDebugClient, &quot;.loadby sos mscorwks&quot;, TRUE);
            hr = Execute(pDebugClient, &quot;.cordll -l&quot;, TRUE);
            goto CleanUp;
        }

        // .NET 4.0
        hr = pDebugSymbols-&gt;GetModuleByModuleName(&quot;clr&quot;, 0, &amp;nIndex, NULL);
        if ((hr == S_OK) &amp;&amp; (nIndex !=0xFFFF))
        {
            hr = Execute(pDebugClient, &quot;.loadby sos clr&quot;, TRUE);
            hr = Execute(pDebugClient, &quot;.cordll -l&quot;, TRUE);
            goto CleanUp;
        }

        // Silverlight
        hr = pDebugSymbols-&gt;GetModuleByModuleName(&quot;coreclr&quot;, 0, &amp;nIndex, NULL);
        if ((hr == S_OK) &amp;&amp; (nIndex !=0xFFFF))
        {
            hr = Execute(pDebugClient, &quot;.loadby sos coreclr&quot;, TRUE);
            hr = Execute(pDebugClient, &quot;.cordll -l&quot;, TRUE);
            goto CleanUp;
        }
CleanUp:
        pDebugSymbols-&gt;Release();
    }
    return hr;
}
extern &quot;C&quot; HRESULT CALLBACK
DebugExtensionInitialize(PULONG Version, PULONG Flags)
{
    *Version = DEBUG_EXTENSION_VERSION(EXT_MAJOR_VER, EXT_MINOR_VER);
    *Flags = 0;  // Reserved for future use.

    HRESULT hr = S_OK;
    IDebugClient* pDebugClient;
    hr = DebugCreate(__uuidof(IDebugClient), (void **)&amp;pDebugClient);
    if (hr == S_OK)
    {
        // Load SOS and do .cordll
        loadsos(pDebugClient, NULL);
        pDebugClient-&gt;Release();
    }
    return hr;
}
</pre></p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634886014613985564</link>
		<pubDate>Thu, 15 Nov 2012 18:37:41 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634886014613985564</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[Andrew&#58; Thanks for the info&#33;<p>posted by Cyberbrad</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634886026120632395</link>
		<pubDate>Thu, 15 Nov 2012 18:56:52 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634886026120632395</guid>
		<dc:creator>Cyberbrad</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>Andrew... awesome demo. I have been trying to follow along, however I run into a weird problem with procdump 5.0. I have a simple divide by zero crash app (C# &nbsp;.NET 4) however when it is executed procdump does not write the dump file. I have set up my environment as prescribed but no luck. Can you help a novice?</p><p>posted by dcrearer</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634887715668249430</link>
		<pubDate>Sat, 17 Nov 2012 17:52:46 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634887715668249430</guid>
		<dc:creator>dcrearer</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>I get the following status when using .ecxr - Unable to get exception context, HRESULT 0x8000FFFF.</p><p>Does the .prefer_dml 1 registry command only work on dump files?</p><p>posted by dcrearer</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634887733411980878</link>
		<pubDate>Sat, 17 Nov 2012 18:22:21 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634887733411980878</guid>
		<dc:creator>dcrearer</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634887715668249430">dcrearer</a>: Divide by Zero is a special case - the CPU doesn't throw them as an exception. I looked in to this briefly while making the test apps for ProcDump, and didn't come to a solution.</p><p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634887733411980878">dcrearer</a>: You can only do .ecxr if an exception context record has been added to dump by the dump creator. A hang dump (for example) won't have one.&nbsp; In this case, you only have the context of when the dump was taken.</p><p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634887733411980878">dcrearer</a>: .prefer_dml 1 works in all scenarios.&nbsp; It isn't dependant on live vs. dump, or user vs. kernel.&nbsp; If you launch windbg via the .dmp association, then yes, the -c &quot;.prefer_dml 1&quot; will be executed from the command key. For manual, make a&nbsp;shortcut to windbg with the -c &quot;.prefer_dml 1&quot; added to the command line.</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634888589937986779</link>
		<pubDate>Sun, 18 Nov 2012 18:09:53 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634888589937986779</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>Andrew... Thanks much for your feedback... Its greatly appreciated.</p><p>posted by dcrearer</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634888869391040529</link>
		<pubDate>Mon, 19 Nov 2012 01:55:39 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634888869391040529</guid>
		<dc:creator>dcrearer</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634884244360676898">windev</a>: Andrew - I just downloaded the new ProcDump 5.1 and it throws this exception when I try and run it:&nbsp; &quot;Entry Point Not Found - The procedure entry point RegGetValueW could not be located in the dynamic link library ADVAPI32.dll.&quot;.&nbsp; I have tried it on 4 different Windows XP x86 PCs and each gave the same error.&nbsp; They all seem to run 5.0 fine.</p><p>I did some searching and it looks like RegGetValue() is only available on Win XP x64, Vista, and newer, so that might be the problem (MSDN link below).&nbsp; It worked fine on the Win 7 x86 and x64 PCs I tried it on.&nbsp; Did you update the code used to read the EulaAccepted value out of &quot;HKEY_CURRENT_USER\Software\Sysinternals\ProcDump&quot;?</p><p>RegGetValue function (Windows)</p><p><a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms724868%28v=vs.85%29.aspx">http&#58;&#47;&#47;msdn.microsoft.com&#47;en-us&#47;library&#47;windows&#47;desktop&#47;ms724868&#37;28v&#61;vs.85&#37;29.aspx</a></p><p>posted by Cyberbrad</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634890481358421068</link>
		<pubDate>Tue, 20 Nov 2012 22:42:15 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634890481358421068</guid>
		<dc:creator>Cyberbrad</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634890481358421068">Cyberbrad</a>: This might be by-product of the registry operations used in the new JIT support (-i &lt;folder&gt;).&nbsp;For now use v5.0 on WinXP SP3 x86 while I work on a fix. Thanks for reporting it.</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634890620389852518</link>
		<pubDate>Wed, 21 Nov 2012 02:33:58 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634890620389852518</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634890620389852518">windev</a>: Will do.&nbsp; Thanks</p><p>&nbsp;</p><p>posted by Cyberbrad</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634891070460360828</link>
		<pubDate>Wed, 21 Nov 2012 15:04:06 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634891070460360828</guid>
		<dc:creator>Cyberbrad</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[I just wanted to pipe up at this point and confirm that I am also seeing &#34;Entry Point Not Found - The procedure entry point RegGetValueW could not be located in the dynamic link library ADVAPI32.dll.&#34; when I try to run procdump 5.1 on any 32 bit Windows XP machine.<br><br>&#64;windev&#58; you say you&#39;re working on a fix.  Any idea when that might be available&#63;  As for running procdump 5.0&#58; I&#39;d love to, but can&#39;t find it anywhere. Is there a sysinternals archive somewhere&#63;<p>posted by Jeff Rivett</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634893735793091912</link>
		<pubDate>Sat, 24 Nov 2012 17:06:19 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634893735793091912</guid>
		<dc:creator>Jeff Rivett</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634890481358421068">Cyberbrad</a>&nbsp;and @<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634893735793091912">Jeff Rivett</a>:&nbsp; Mark found and fixed the bug in ProcDump v5.1 over the weekend (I used RegGetValue in the new Silverlight code). I've asked Mark to accelerate the publishing of it externally.</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634895510890937520</link>
		<pubDate>Mon, 26 Nov 2012 18:24:49 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634895510890937520</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634895510890937520">windev</a>:&nbsp; ProcDump v5.11 got released yesterday to fix the WinXP compatibility issue.</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634903465367128893</link>
		<pubDate>Wed, 05 Dec 2012 23:22:16 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634903465367128893</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>@<a href="/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634903465367128893">windev</a>: ProcDump v5.13 got released today to fix another WinXP compatibility issue. ProcDump was trying to use a DbgHelp v6.1 feature when running just with DbgHelp v5.1 from WinXP's System32 folder.</p><p>posted by windev</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634946668556337097</link>
		<pubDate>Thu, 24 Jan 2013 23:27:35 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634946668556337097</guid>
		<dc:creator>windev</dc:creator>
	</item>
	<item>
		<title>Re: Defrag Tools: #14 - WinDbg - SOS</title>
		<description>
			<![CDATA[<p>Amazing series! Thank you!</p><p>posted by Evginnie</p>]]>
		</description>
		<link>http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634969481468365602</link>
		<pubDate>Wed, 20 Feb 2013 09:09:06 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-14-WinDbg-SOS#c634969481468365602</guid>
		<dc:creator>Evginnie</dc:creator>
	</item>
</channel>
</rss>