<?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: Application Specific Information in Leopard Crash Reports</title>
	<atom:link href="http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/</link>
	<description>happenings in the world of proton</description>
	<lastBuildDate>Fri, 23 Jul 2010 18:22:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sigbus</title>
		<link>http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/comment-page-1/#comment-4310</link>
		<dc:creator>sigbus</dc:creator>
		<pubDate>Thu, 18 Mar 2010 03:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/#comment-4310</guid>
		<description>[...] PHP modules but signal 4 was something new to me. ... Mail (will not be published) (required) ...allocinit Blog Archive Application Specific Information ...Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at ... Mail (will [...]</description>
		<content:encoded><![CDATA[<p>[...] PHP modules but signal 4 was something new to me. &#8230; Mail (will not be published) (required) &#8230;allocinit Blog Archive Application Specific Information &#8230;Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at &#8230; Mail (will [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Sanders</title>
		<link>http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/comment-page-1/#comment-3269</link>
		<dc:creator>Paul Sanders</dc:creator>
		<pubDate>Tue, 20 Oct 2009 09:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/#comment-3269</guid>
		<description>But they&#039;re not going to change it, are they?  This mechanism is already used by AppKit on Leopard to report fatal program conditions in CrashReporter.  If Apple change it in future OS X releases, this behaviour would break and that would be Shooting Yourself In the Foot.  I think that just checking that the symbol exists is enough.

Nice piece of detective work, by the way.  Handy to know.</description>
		<content:encoded><![CDATA[<p>But they&#8217;re not going to change it, are they?  This mechanism is already used by AppKit on Leopard to report fatal program conditions in CrashReporter.  If Apple change it in future OS X releases, this behaviour would break and that would be Shooting Yourself In the Foot.  I think that just checking that the symbol exists is enough.</p>
<p>Nice piece of detective work, by the way.  Handy to know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger on Better Logic &#187; Blog Archive &#187; leopard how to display a crash report</title>
		<link>http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/comment-page-1/#comment-862</link>
		<dc:creator>Roger on Better Logic &#187; Blog Archive &#187; leopard how to display a crash report</dc:creator>
		<pubDate>Mon, 02 Jun 2008 16:45:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/#comment-862</guid>
		<description>[...] here open up utilities/console, go to system.log, at the bottom [right after a crash] it will say where [...]</description>
		<content:encoded><![CDATA[<p>[...] here open up utilities/console, go to system.log, at the bottom [right after a crash] it will say where [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahruman’s Webthing &#187; Blog Archive &#187; Hacking your Crash Reports</title>
		<link>http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/comment-page-1/#comment-268</link>
		<dc:creator>Ahruman’s Webthing &#187; Blog Archive &#187; Hacking your Crash Reports</dc:creator>
		<pubDate>Tue, 18 Mar 2008 02:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.allocinit.net/blog/2008/01/04/application-specific-information-in-leopard-crash-reports/#comment-268</guid>
		<description>[...] warranted investigation, and through the powers of Google it was determined that said investigation had in fact happened a few months ago. How fortunate that we didn’t spend time investigating it and writing test cases, only to find [...]</description>
		<content:encoded><![CDATA[<p>[...] warranted investigation, and through the powers of Google it was determined that said investigation had in fact happened a few months ago. How fortunate that we didn’t spend time investigating it and writing test cases, only to find [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
