<?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>Random ICorDebugThread trivia</title><link>http://blogs.msdn.com/b/jmstall/archive/2006/02/01/icordebugthread-trivia.aspx</link><description>Here's random information about ICorDebugThread that I hope eventually makes it into MSDN: 1. The managed CreateThread callback comes at the first bit of managed code that a thread runs. (I think this is a bad for these reasons , and instead it should</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Fake attach event ordering</title><link>http://blogs.msdn.com/b/jmstall/archive/2006/02/01/icordebugthread-trivia.aspx#1372353</link><pubDate>Thu, 28 Dec 2006 09:36:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1372353</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>&lt;p&gt;When you attach to a managed debuggee (via ICorDebug::DebugActiveProcess), ICorDebug generates a set&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1372353" width="1" height="1"&gt;</description></item><item><title>Random ICorDebug trivia about debugging AppDomains </title><link>http://blogs.msdn.com/b/jmstall/archive/2006/02/01/icordebugthread-trivia.aspx#647713</link><pubDate>Mon, 26 Jun 2006 22:47:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:647713</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>I've gotten some questions about how appdomains are handled at the ICorDebug level. Here's some random...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=647713" width="1" height="1"&gt;</description></item><item><title>What to expect when you Attach, Async-Break</title><link>http://blogs.msdn.com/b/jmstall/archive/2006/02/01/icordebugthread-trivia.aspx#556706</link><pubDate>Tue, 21 Mar 2006 19:14:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:556706</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>Don't assume that if you have a thread doing a spin-wait, that you can attach / asynchronously-break...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=556706" width="1" height="1"&gt;</description></item><item><title>Why don't the managed Debugging APIs expose the Finalizer thread? </title><link>http://blogs.msdn.com/b/jmstall/archive/2006/02/01/icordebugthread-trivia.aspx#542205</link><pubDate>Thu, 02 Mar 2006 19:49:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:542205</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>That's a fair question. Part of the answer is we don't believe people could use it properly.&amp;amp;amp;nbsp; The...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=542205" width="1" height="1"&gt;</description></item><item><title>Partition of ICorDebug</title><link>http://blogs.msdn.com/b/jmstall/archive/2006/02/01/icordebugthread-trivia.aspx#527342</link><pubDate>Wed, 08 Feb 2006 09:37:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:527342</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>The ICorDebug API (the API for debugging managed apps) is about 70 total interfaces.&amp;amp;amp;nbsp; Here is how...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=527342" width="1" height="1"&gt;</description></item></channel></rss>