<?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>Naming threads in Win32 And .Net</title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx</link><description>When you are debugging an application with multiple threads it can be handy to have a better name than just the thread id. This is simple to do in managed code. There is a property on the Thread object that you can set. It is also possible to do this</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Naming threads in Win32 And .Net</title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx#510922</link><pubDate>Mon, 09 Jan 2006 23:14:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:510922</guid><dc:creator>Len Holgate</dc:creator><description>Steve,&lt;br&gt;&lt;br&gt;If someone were writing a debugging tool and wanted to provide users of the tool with functionality similar to the thread naming shown above (i.e. provide a way for their source code to communicate with the debug tool when it is present) what would be the best way to select a value for the exception code? I'm currently assuming that there isn't really a great deal to do except pick a value that an application programmer who decided to define their own exception code (and I expect they're few and far between) is unlikely to pick...   </description></item><item><title>re: Naming threads in Win32 And .Net</title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx#515117</link><pubDate>Fri, 20 Jan 2006 02:50:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:515117</guid><dc:creator>SteveJS</dc:creator><description>Len,&lt;br&gt;&lt;br&gt;Yes, basically a random exception code is what you want.  If you do have a collision with one picked by an application programmer I believe there are only two concerns: &lt;br&gt;&lt;br&gt;1. If the app programmer uses a Vectored Exception handler that tries to handle that exception code. Then use of your diagnostic function will change the app behavior.  However, installing a vectored exception handler is not typical and anyone who does had better make sure they know what they are doing.  They should take into account diagnostic functions compiled into the code.&lt;br&gt;&lt;br&gt;2. Your debugging tool could get confused by the applications use of the exception code.&lt;br&gt;Basically the fact that no one will pick the same random exception code is probably good enough for most purposes.  &lt;br&gt;However, strictly speaking the exception code is only used to give you the opportunity to look in the target's address space.  You should fail gracefully when the data you want is not there.  Since your debugger is looking at a buggy process there is always the possiblity that a errant thread trashed the memory you need.</description></item><item><title>re: Naming threads in Win32 And .Net</title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx#515715</link><pubDate>Sat, 21 Jan 2006 14:28:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:515715</guid><dc:creator>Len Holgate</dc:creator><description>Steve&lt;br&gt;&lt;br&gt;Thanks.</description></item><item><title>Why don't the managed Debugging APIs expose the Finalizer thread? </title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx#542204</link><pubDate>Thu, 02 Mar 2006 19:49:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:542204</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...</description></item><item><title>Win64 Thread Naming</title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx#557344</link><pubDate>Wed, 22 Mar 2006 02:26:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:557344</guid><dc:creator>andypennell</dc:creator><description>Hey Steve, you should update this with the Win64-compatible version, which I recall has some weird packing for back-compatibility.</description></item><item><title>Naming threads &amp;laquo; Tweaker</title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx#9542996</link><pubDate>Fri, 10 Apr 2009 13:45:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9542996</guid><dc:creator>Naming threads &amp;laquo; Tweaker</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://thetweaker.wordpress.com/2009/04/10/naming-threads/"&gt;http://thetweaker.wordpress.com/2009/04/10/naming-threads/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Visual Studio Debugging Resources</title><link>http://blogs.msdn.com/stevejs/archive/2005/12/19/505815.aspx#9700135</link><pubDate>Thu, 04 Jun 2009 22:44:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9700135</guid><dc:creator>Canadian Developer Connection</dc:creator><description>&lt;p&gt;Articles and Blog Posts Naming threads in Win32 And .NET (Steve Steiner) Reference and Sites Debugging&lt;/p&gt;
</description></item></channel></rss>