<?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>A Tour of Windows CE Performance Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx</link><description>Posted by: Sue Loh What use is a tool if you don't know it's there? One of the problems we have is getting the word out about the tools you can use to debug various kinds of problems. We honestly do try to figure out how to arrange our help documentation</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: A Tour of Windows CE Performance Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#499285</link><pubDate>Fri, 02 Dec 2005 11:30:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:499285</guid><dc:creator>Gursharan</dc:creator><description>From now onwards, please take the prefix &amp;quot;excellent&amp;quot; to my evry reply for your posts by default. One thing that is interesting here is the level at which these tools work. If we move in the hierarchy, application-&amp;gt;kernel-&amp;gt;HAL-&amp;gt;Hardware, I guess the tools like Kernel tracker dig just &amp;quot;below&amp;quot; the kernel and scrape off bits of kernel and processor interaction. Hope it makes some sense!&lt;br&gt;</description></item><item><title>re: A Tour of Windows CE Performance Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#499387</link><pubDate>Fri, 02 Dec 2005 18:44:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:499387</guid><dc:creator>sloh</dc:creator><description>Thanks Gursharan.  Actually I would say that the tools are just at the kernel level, or in some cases the application.&lt;br&gt;&lt;br&gt;Sue</description></item><item><title>re: A Tour of Windows CE Performance Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#500027</link><pubDate>Mon, 05 Dec 2005 13:52:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:500027</guid><dc:creator>Andrew Worsley</dc:creator><description>I have used Kernel Tracker recently - great tool! You say that all modules being profiled need to be in ROM, but I was using it to see what an application was doing (relative to device drivers &amp;amp; interrupts). The application was being loaded from a CompactFlash card, so it definitely wasn't in ROM. Admittedly the threads of the app just had thread IDs to identify them (not thread function names like those in the OS), but it was useful for app debugging nonetheless...</description></item><item><title>re: A Tour of Windows CE Performance Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#512339</link><pubDate>Fri, 13 Jan 2006 04:56:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:512339</guid><dc:creator>ce_base</dc:creator><description>Actually to use Kernel Tracker, the modules don't have to be in ROM.  That's only for the Monte Carlo profiler.  Yeah the thread names are the main thing that you lose in Kernel Tracker if your application is not in ROM.  For what it's worth: Starting from about CE 5.0, the readlog.exe desktop-side tool has a &amp;quot;-fixthreads&amp;quot; parameter that'll make it spit out a new log with fixed-up thread names.  It parses the .map files from your release directory to get the symbols to make thread names.&lt;br&gt;&lt;br&gt;Sue</description></item><item><title>re: A Tour of Windows CE Performance Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#516618</link><pubDate>Tue, 24 Jan 2006 06:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:516618</guid><dc:creator>ce_base</dc:creator><description>Also see my memory tool post:&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/ce_base/archive/2006/01/11/511883.aspx"&gt;http://blogs.msdn.com/ce_base/archive/2006/01/11/511883.aspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;Sue</description></item><item><title>re: A Tour of Windows CE Performance Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#516912</link><pubDate>Tue, 24 Jan 2006 20:46:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:516912</guid><dc:creator>Mike Gio</dc:creator><description>Now that Remote Call Profiler and some of the other tools have been removed from VC 2005 is there any way for ISV's to do performance analysis for their applications running under Windows CE? I really wish I had this program. It seemed to exactly what I needed. </description></item><item><title>Windows CE Base Team Blog : A Tour of Windows CE Memory Tools</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#532582</link><pubDate>Wed, 15 Feb 2006 19:18:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:532582</guid><dc:creator>Windows CE Base Team Blog : A Tour of Windows CE Memory Tools</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/ce_base/archive/2006/01/11/511883.aspx"&gt;http://blogs.msdn.com/ce_base/archive/2006/01/11/511883.aspx&lt;/a&gt;</description></item><item><title>Troubleshooting guide - part 2</title><link>http://blogs.msdn.com/ce_base/archive/2005/11/30/a-tour-of-windows-ce-performance-tools.aspx#9559272</link><pubDate>Tue, 21 Apr 2009 17:09:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9559272</guid><dc:creator>HoppeRx - the cure for your ailing device</dc:creator><description>&lt;p&gt;Below is the second half of a well executed document from guestRx: Bulent Elmaci. Bulent has worked with&lt;/p&gt;
</description></item></channel></rss>