<?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: Stabs is deprecated</title>
	<atom:link href="http://lapcatsoftware.com/blog/2008/03/09/stabs-is-deprecated/feed/" rel="self" type="application/rss+xml" />
	<link>http://lapcatsoftware.com/blog/2008/03/09/stabs-is-deprecated/</link>
	<description>Coding under the close supervision of cats</description>
	<pubDate>Sat, 22 Nov 2008 09:00:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Marc Charbonneau&#8217;s Blog &#187; Cocoa development links of interest</title>
		<link>http://lapcatsoftware.com/blog/2008/03/09/stabs-is-deprecated/#comment-6956</link>
		<dc:creator>Marc Charbonneau&#8217;s Blog &#187; Cocoa development links of interest</dc:creator>
		<pubDate>Tue, 11 Mar 2008 15:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://lapcatsoftware.com/blog/2008/03/09/stabs-is-deprecated/#comment-6956</guid>
		<description>[...] Jeff Johnson: With STABS, you could build the release version of your app with debugging symbols, make a copy of the executable MyApp.app/Contents/MacOS/MyApp to keep, strip the executable for shipping, and then use the unstripped executable for symbolizing crash reports by giving a space-separated list of stack trace addresses to the command-line tool atos. Unfortunately, atos cannot currently serve this purpose with DWARF. Unlike STABS, DWARF does not include the debugging symbols in the executable itself but merely includes references to the intermediate object files, which do contain debugging symbols. You can usually find these .o files in a sub-directory of the build/MyApp.build directory. If you delete the object files after building with dwarf, you won’t be able to step through your app’s code. (With stabs, the object files are refuse.) You also won’t be able to step through the code if you strip debugging symbols from your app, even if you keep the object files, because the references to the object files will be gone from the executable. [...]</description>
		<content:encoded><![CDATA[<p>[...] Jeff Johnson: With STABS, you could build the release version of your app with debugging symbols, make a copy of the executable MyApp.app/Contents/MacOS/MyApp to keep, strip the executable for shipping, and then use the unstripped executable for symbolizing crash reports by giving a space-separated list of stack trace addresses to the command-line tool atos. Unfortunately, atos cannot currently serve this purpose with DWARF. Unlike STABS, DWARF does not include the debugging symbols in the executable itself but merely includes references to the intermediate object files, which do contain debugging symbols. You can usually find these .o files in a sub-directory of the build/MyApp.build directory. If you delete the object files after building with dwarf, you won’t be able to step through your app’s code. (With stabs, the object files are refuse.) You also won’t be able to step through the code if you strip debugging symbols from your app, even if you keep the object files, because the references to the object files will be gone from the executable. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stabs is deprecated &#171; JongAm&#8217;s blog</title>
		<link>http://lapcatsoftware.com/blog/2008/03/09/stabs-is-deprecated/#comment-6927</link>
		<dc:creator>Stabs is deprecated &#171; JongAm&#8217;s blog</dc:creator>
		<pubDate>Mon, 10 Mar 2008 02:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://lapcatsoftware.com/blog/2008/03/09/stabs-is-deprecated/#comment-6927</guid>
		<description>[...] is&#160;deprecated According to Lap Cat Software Blog, the Stabs is [...]</description>
		<content:encoded><![CDATA[<p>[...] is&nbsp;deprecated According to Lap Cat Software Blog, the Stabs is [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
