<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: GDB tools for intel debugging</title>
	<atom:link href="http://kevin.sb.org/2006/02/23/gdb-tools-for-intel-debugging/feed/" rel="self" type="application/rss+xml" />
	<link>http://kevin.sb.org/2006/02/23/gdb-tools-for-intel-debugging/</link>
	<description>The occasional view into my life</description>
	<pubDate>Fri, 05 Dec 2008 08:19:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Daniel Jalkut</title>
		<link>http://kevin.sb.org/2006/02/23/gdb-tools-for-intel-debugging/#comment-73</link>
		<dc:creator>Daniel Jalkut</dc:creator>
		<pubDate>Sun, 26 Feb 2006 10:52:56 +0000</pubDate>
		<guid isPermaLink="false">68bb4d09-74fe-40ad-90e6-3cd04fb1a0ff#comment-73</guid>
		<description>Nice stuff, Kevin. You're paving the way for a smooth transition to Intel debugging!

PS I like this blog's template, too. The big sectional labels make it really easy to navigate. Blog envy!</description>
		<content:encoded><![CDATA[	<p>Nice stuff, Kevin. You&#8217;re paving the way for a smooth transition to Intel debugging!</p>
	<p>PS I like this blog&#8217;s template, too. The big sectional labels make it really easy to navigate. Blog envy!</p>

 ]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ballard</title>
		<link>http://kevin.sb.org/2006/02/23/gdb-tools-for-intel-debugging/#comment-72</link>
		<dc:creator>Kevin Ballard</dc:creator>
		<pubDate>Fri, 24 Feb 2006 04:19:55 +0000</pubDate>
		<guid isPermaLink="false">68bb4d09-74fe-40ad-90e6-3cd04fb1a0ff#comment-72</guid>
		<description>Oh oops, I forgot I had some non-breaking spaces in there (otherwise gdb ignores the blank lines in the doc strings). It's UTF-8. I'll fix the file to be ASCII-only instead. Sorry 'bout that.</description>
		<content:encoded><![CDATA[	<p>Oh oops, I forgot I had some non-breaking spaces in there (otherwise gdb ignores the blank lines in the doc strings). It&#8217;s UTF-8. I&#8217;ll fix the file to be ASCII-only instead. Sorry &#8216;bout that.</p>

 ]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Udey</title>
		<link>http://kevin.sb.org/2006/02/23/gdb-tools-for-intel-debugging/#comment-71</link>
		<dc:creator>Dan Udey</dc:creator>
		<pubDate>Fri, 24 Feb 2006 03:39:29 +0000</pubDate>
		<guid isPermaLink="false">68bb4d09-74fe-40ad-90e6-3cd04fb1a0ff#comment-71</guid>
		<description>The encoding seems to be UTF-8 from this end, no problems here. If you're getting weird individual characters (i.e. a strange block in the middle of a word), then it's generally non-unicode being misinterpreted as unicode. If you see pairs of high-ascii instead of letters, then it's generally the opposite.</description>
		<content:encoded><![CDATA[	<p>The encoding seems to be UTF-8 from this end, no problems here. If you&#8217;re getting weird individual characters (i.e. a strange block in the middle of a word), then it&#8217;s generally non-unicode being misinterpreted as unicode. If you see pairs of high-ascii instead of letters, then it&#8217;s generally the opposite.</p>

 ]]></content:encoded>
	</item>
	<item>
		<title>By: Dan wood</title>
		<link>http://kevin.sb.org/2006/02/23/gdb-tools-for-intel-debugging/#comment-70</link>
		<dc:creator>Dan wood</dc:creator>
		<pubDate>Fri, 24 Feb 2006 03:30:04 +0000</pubDate>
		<guid isPermaLink="false">68bb4d09-74fe-40ad-90e6-3cd04fb1a0ff#comment-70</guid>
		<description>What's the character encoding on that -- I'm seeing some "gremlins" when viewing it ... </description>
		<content:encoded><![CDATA[	<p>What&#8217;s the character encoding on that&#8212;I&#8217;m seeing some &#8220;gremlins&#8221; when viewing it &#8230;</p>

 ]]></content:encoded>
	</item>
</channel>
</rss>
