<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: IMVU&#8217;s CallStack API Now Open Source!</title>
	<atom:link href="http://chadaustin.me/2009/04/imvus-callstack-api-now-open-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://chadaustin.me/2009/04/imvus-callstack-api-now-open-source/</link>
	<description></description>
	<lastBuildDate>Sun, 22 Jan 2012 21:02:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chad Austin</title>
		<link>http://chadaustin.me/2009/04/imvus-callstack-api-now-open-source/comment-page-1/#comment-6494</link>
		<dc:creator>Chad Austin</dc:creator>
		<pubDate>Mon, 08 Jun 2009 22:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://aegisknight.org/?p=1318#comment-6494</guid>
		<description>Great.  :)  It turns out that almost everybody reimplements this stuff.  Google has their breakpad API, but it&#039;s not a general solution.  Maybe we should fold CallStack into breakpad?</description>
		<content:encoded><![CDATA[<p>Great.  :)  It turns out that almost everybody reimplements this stuff.  Google has their breakpad API, but it&#8217;s not a general solution.  Maybe we should fold CallStack into breakpad?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeff russell</title>
		<link>http://chadaustin.me/2009/04/imvus-callstack-api-now-open-source/comment-page-1/#comment-6492</link>
		<dc:creator>jeff russell</dc:creator>
		<pubDate>Mon, 08 Jun 2009 19:36:24 +0000</pubDate>
		<guid isPermaLink="false">http://aegisknight.org/?p=1318#comment-6492</guid>
		<description>Cool! I ended up implementing almost the exact same thing for DoD... but it would just try to translate the symbols on the spot (which meant our dev team needed .pdb files around). Translating the addresses later would make the tool a bit more useful, good idea!</description>
		<content:encoded><![CDATA[<p>Cool! I ended up implementing almost the exact same thing for DoD&#8230; but it would just try to translate the symbols on the spot (which meant our dev team needed .pdb files around). Translating the addresses later would make the tool a bit more useful, good idea!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

