<?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>Very Advanced Debugging tips</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx</link><description>While debugging code, it might take very many complicated steps to reproduce an issue. The following applies to debugging both Visual FoxPro and Visual Studio Native code debugging, except where noted. The VFP debugger is modeled after the VS debugger</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Overload Operator new to detect memory leaks</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#9341634</link><pubDate>Tue, 20 Jan 2009 05:48:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9341634</guid><dc:creator>Calvin Hsia's WebLog</dc:creator><description>&lt;p&gt;There are various leak detection methods for memory allocators. A popular one is to tag each allocation&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9341634" width="1" height="1"&gt;</description></item><item><title>VC++ debugging in 2003, Can not see values of all the variables</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#1795595</link><pubDate>Sat, 03 Mar 2007 14:03:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1795595</guid><dc:creator>Rajeev</dc:creator><description>&lt;p&gt;While I am dubugging a very large code (15000 lines) in VC++, for some of the local variables, it does NOT show the value while debugging. Is there some setting I need to do so that I can see the values of all the variables while debugging?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1795595" width="1" height="1"&gt;</description></item><item><title>How to log application API calls using import module addresses </title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#1764668</link><pubDate>Mon, 26 Feb 2007 21:44:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1764668</guid><dc:creator>Calvin Hsia's WebLog</dc:creator><description>&lt;p&gt;Let’s log all the calls that Excel makes to open or create a file. Start Visual Studio (any version),&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1764668" width="1" height="1"&gt;</description></item><item><title>re: Very Advanced Debugging tips</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#814374</link><pubDate>Wed, 11 Oct 2006 00:09:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:814374</guid><dc:creator>Mr. Raybell</dc:creator><description>&lt;p&gt;Does modifying the registers only work in native debugging, or can you modify them in managed debugging as well? &amp;nbsp;If so, I can't manage to figure out how to work it, so perhaps I'm missing something? &amp;nbsp;It'd be horribly handy for what I'm doing right now.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=814374" width="1" height="1"&gt;</description></item><item><title>re: Very Advanced Debugging tips</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#702865</link><pubDate>Wed, 16 Aug 2006 22:00:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:702865</guid><dc:creator>Arya</dc:creator><description>In case of debugging watson crash dumps ... what do we need to look for in the disassembly! I am new at this, so please explain in detail...&lt;br&gt;&lt;br&gt;Thanks!&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=702865" width="1" height="1"&gt;</description></item><item><title>What API calls reset GetLastError between Declare DLL calls in VFP8?</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#589351</link><pubDate>Wed, 03 May 2006 21:32:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:589351</guid><dc:creator>Calvin Hsia's WebLog</dc:creator><description>I received a comment on this post: Will GetLastError ever work properly in VFP8.0?. &amp;amp;amp;nbsp;I was consistently...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=589351" width="1" height="1"&gt;</description></item><item><title>Customize the VS debugger display of your data</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#525976</link><pubDate>Tue, 07 Feb 2006 00:04:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:525976</guid><dc:creator>Calvin Hsia's WebLog</dc:creator><description>As a software developer, I spend much of my time looking at code, learning how it works, and figuring...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=525976" width="1" height="1"&gt;</description></item><item><title>Another customer problem: a product doesn't work with VFP</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#274762</link><pubDate>Sat, 04 Dec 2004 02:56:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:274762</guid><dc:creator>Calvin Hsia's WebLog</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=274762" width="1" height="1"&gt;</description></item><item><title>Another customer problem: a product doesn't work with VFP</title><link>http://blogs.msdn.com/b/calvin_hsia/archive/2004/10/22/246382.aspx#274681</link><pubDate>Sat, 04 Dec 2004 00:49:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:274681</guid><dc:creator>Calvin Hsia's WebLog</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=274681" width="1" height="1"&gt;</description></item></channel></rss>