<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx</link><description>The purpose of this blog is to provide you with information that will help you during debugging sessions. The debugging toolbox I provide is a collection of Windbg scripts I created to help me on a daily basis. The collection expands whenever I develop</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Scripting WINDBG</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#1910814</link><pubDate>Mon, 19 Mar 2007 06:42:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1910814</guid><dc:creator>Mike Hoover</dc:creator><description>&lt;p&gt;Really a quality work! This is awsome, I have heard about it but actually never read about it, this is the first blog I see related to the topic.&lt;/p&gt;</description></item><item><title>re: Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#1914345</link><pubDate>Mon, 19 Mar 2007 22:57:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1914345</guid><dc:creator>Roberto Farah</dc:creator><description>&lt;p&gt;Thanks Mike! &lt;/p&gt;</description></item><item><title>re: Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#5471680</link><pubDate>Tue, 16 Oct 2007 17:31:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5471680</guid><dc:creator>nickx</dc:creator><description>&lt;P&gt;your work is appreciated.&lt;/P&gt;</description></item><item><title>[Windbg Script] Retrieving information from ASP</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856761</link><pubDate>Tue, 25 Dec 2007 03:41:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856761</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;Have you ever had this situation: You need to get ASP information from an IIS process? If yes, you can&lt;/p&gt;
</description></item><item><title>[Windbg Script] Playing with Minesweeper</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856762</link><pubDate>Tue, 25 Dec 2007 03:42:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856762</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;First, this script is not really about cheating. It does that with Minesweeper, but there are several&lt;/p&gt;
</description></item><item><title>[Windbg Script] Playing with Notepad</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856784</link><pubDate>Tue, 25 Dec 2007 03:44:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856784</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;This is one of my “just for fun” scripts. It’s very simple and has some limitations, but it’s fun! What&lt;/p&gt;
</description></item><item><title>[Windbg Script] Tracing API calls</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856787</link><pubDate>Tue, 25 Dec 2007 03:44:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856787</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;This is a very simple script, yet powerful script. You can use it to see the APIs an application is using&lt;/p&gt;
</description></item><item><title>[Windbg Script] Extracting Performance Monitor counters from .NET application</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856788</link><pubDate>Tue, 25 Dec 2007 03:44:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856788</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;Have you ever had a situation where you find yourself debugging a dump from ASP.NET when suddenly you&lt;/p&gt;
</description></item><item><title>[Windbg Script] Tracing MessageBox calls</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856789</link><pubDate>Tue, 25 Dec 2007 03:45:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856789</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;In the past I worked on a support case where I needed to find out if some MessageBox from a C++ application&lt;/p&gt;
</description></item><item><title>[Windbg Script] Saving a Module - Extracting Base Address and Image Name from a method call</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856836</link><pubDate>Tue, 25 Dec 2007 03:47:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856836</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;After creating this script, I have used it in almost every case that requires decompilation, and I guess&lt;/p&gt;
</description></item><item><title>[Windbg Script] Disassembling Routines and Searching for Instructions</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#6856838</link><pubDate>Tue, 25 Dec 2007 03:47:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6856838</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;Sometimes you cannot avoid reading the disassembled code to look for a specific assembly instruction.&lt;/p&gt;
</description></item><item><title>re: Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#8577912</link><pubDate>Fri, 06 Jun 2008 16:45:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8577912</guid><dc:creator>sandeep</dc:creator><description>&lt;p&gt;Thanks!! it is a great help.&lt;/p&gt;</description></item><item><title>re: Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#8714704</link><pubDate>Thu, 10 Jul 2008 04:49:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8714704</guid><dc:creator>Toyota</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for the nice info!&lt;/p&gt;
&lt;p&gt;By the way, you said;&lt;/p&gt;
&lt;p&gt;&amp;quot;It will be fixed in the future, anyway,...&amp;quot;&lt;/p&gt;
&lt;p&gt;Does this mean that the current script engine has some problems?&lt;/p&gt;</description></item><item><title>re: Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#8714808</link><pubDate>Thu, 10 Jul 2008 05:27:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8714808</guid><dc:creator>Roberto Farah</dc:creator><description>&lt;p&gt;Hi Toyota,&lt;/p&gt;
&lt;p&gt;The scripts are ok, no problems found and when someone finds a bug I try to fix it as soon as possible, however, WinDbg had (and has) some issues when running scripts, for example, when you run a script that has alias and call it again you get an error. If you want to verify it by yourself, use, for example, dig_stack.txt, then call it again. Most of the problems I'm aware of were already fixed.&lt;/p&gt;
&lt;p&gt;Lately I'm creating scripts using PowerShell that offer much more resources, stability and power. In a few weeks I'll post the newest PowerDbg library and a new script. Keep one eye in my blog. :)&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;</description></item><item><title>re: Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#8714973</link><pubDate>Thu, 10 Jul 2008 06:15:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8714973</guid><dc:creator>Toyota</dc:creator><description>&lt;p&gt;To Mr.Farah,&lt;/p&gt;
&lt;p&gt;&amp;gt; Lately I'm creating scripts using PowerShell that&lt;/p&gt;
&lt;p&gt;&amp;gt; offer much more resources, stability and power. In a &lt;/p&gt;
&lt;p&gt;&amp;gt; few weeks I'll post the newest PowerDbg library and a &lt;/p&gt;
&lt;p&gt;&amp;gt; new script. Keep one eye in my blog. :)&lt;/p&gt;
&lt;p&gt;This is great!&lt;/p&gt;
&lt;p&gt;I cannot wait any longer!!!&lt;/p&gt;
&lt;p&gt;Thank you for your answer. I will try dig_stack.txt.&lt;/p&gt;</description></item><item><title>[Debugging Toolbox]Read Me</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#8923592</link><pubDate>Thu, 04 Sep 2008 07:55:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8923592</guid><dc:creator>!analyze -v</dc:creator><description>&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx"&gt;http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx&lt;/a&gt; 글 : Roberto Alexis Farah 번역 :&lt;/p&gt;
</description></item><item><title>[Windbg Script] Digging the Call Stack</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#9319365</link><pubDate>Wed, 14 Jan 2009 23:31:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9319365</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;Windbg has a lot of commands and command variations, so sometimes you may forget some of them, like when&lt;/p&gt;
</description></item><item><title>[Windbg Script] Get Portable Executable Headers</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#9319373</link><pubDate>Wed, 14 Jan 2009 23:34:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9319373</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;There are several tools you can use to read the image headers, like Dumpbin.exe and Link.exe, for instance.&lt;/p&gt;
</description></item><item><title>[Windbg Script] Retrieving queries/stored procedures from .NET application</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/03/18/read-me.aspx#9319383</link><pubDate>Wed, 14 Jan 2009 23:40:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9319383</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;Ok, you are debugging a .NET application. You need to find out the queries and stored procedures being&lt;/p&gt;
</description></item></channel></rss>