<?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>Why debugging breaks in optimized (production) builds.</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx</link><description>You may have noticed that debugging optimized builds (eg, what you commonly get when you attach to a end-user instance of your app that wasn't launched from your debugging environment) is usually a degraded experience. At an architectural level, there</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Why debugging breaks in optimized (production) builds.</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx#5402043</link><pubDate>Thu, 11 Oct 2007 18:04:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5402043</guid><dc:creator>Mike Stall - MSFT</dc:creator><description>&lt;p&gt;GP - that's some good blog fodder. Stay tuned...&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5402043" width="1" height="1"&gt;</description></item><item><title>The debugger is not just an extension to BCL + Reflection</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx#5396544</link><pubDate>Thu, 11 Oct 2007 06:00:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5396544</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>&lt;p&gt;Don't have your non-debugger app use the debugging services just to get some cool functionality. The&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5396544" width="1" height="1"&gt;</description></item><item><title>re: Why debugging breaks in optimized (production) builds.</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx#5383273</link><pubDate>Tue, 09 Oct 2007 18:35:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5383273</guid><dc:creator>GP</dc:creator><description>&lt;p&gt;What about the /debug:pdbonly /optimize csc.exe switches (Default &amp;quot;Release&amp;quot; Configuration von VS 2005 for C# Projects)? How deals the C# Compiler with the above issues when building the Module and the Symbol-File?&lt;/p&gt;
&lt;p&gt;When a Application is lauched from a Debugger it may be possible to disable Optimization that would be made by the JIT-Compiler.&lt;/p&gt;
&lt;p&gt;But what happens when a Debugger is attached to an already running Application? Methods may be already JITted (and optimized) and the CLR may be in a (internal) state that makes it impossible to start all over without loosing &amp;quot;public&amp;quot; state. So the Symbols will not match in some cases (maybe inlined functions). Or am I wrong?&lt;/p&gt;
&lt;p&gt;This would be a very interesting Subject for another Blog-Entry: &amp;quot;/debug:pdbonly and /debug:full Symbols compared&amp;quot;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5383273" width="1" height="1"&gt;</description></item><item><title>Interesting Finds: October 6, 2007</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx#5317417</link><pubDate>Sat, 06 Oct 2007 18:12:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5317417</guid><dc:creator>Jason Haley</dc:creator><description>&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5317417" width="1" height="1"&gt;</description></item><item><title>re: Why debugging breaks in optimized (production) builds.</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx#5301524</link><pubDate>Sat, 06 Oct 2007 01:22:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5301524</guid><dc:creator>Mike Stall - MSFT</dc:creator><description>&lt;p&gt;Hi Russ. I guess my posts are finally starting to get technical enough again :)&lt;/p&gt;
&lt;p&gt;Re using wrong PDBs: yeah, that's disasterous. Fortunately there's pretty good matching support for a debugger to use (asame with source files). &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5301524" width="1" height="1"&gt;</description></item><item><title>re: Why debugging breaks in optimized (production) builds.</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx#5299257</link><pubDate>Fri, 05 Oct 2007 22:31:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5299257</guid><dc:creator>Russell Osterlund</dc:creator><description>&lt;p&gt;Nice post.&lt;/p&gt;
&lt;p&gt;Many of the reasons that you cite have convinced me that in the long run it is better to debug optimized (production) builds at the disassembly level. &amp;nbsp;I would also suggest that much of the disorientation arises in those whose debugging experience is almost solely at the source code level. &amp;nbsp;Finally, the occasions when you think you are using the correct PDB's, but in fact they do not match the binary are almost worse than having no PDB's in the first place -- you are lulled into a false sense of security.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5299257" width="1" height="1"&gt;</description></item><item><title>Techy News Blog &amp;raquo; Why debugging breaks in optimized (production) builds.</title><link>http://blogs.msdn.com/b/jmstall/archive/2007/10/05/why-debugging-breaks-in-optimized-production-builds.aspx#5295443</link><pubDate>Fri, 05 Oct 2007 19:20:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5295443</guid><dc:creator>Techy News Blog » Why debugging breaks in optimized (production) builds.</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.artofbam.com/wordpress/?p=5494"&gt;http://www.artofbam.com/wordpress/?p=5494&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5295443" width="1" height="1"&gt;</description></item></channel></rss>