<?xml version="1.0"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<atom:link href="http://newsconomy.com/rss/tag/debugging" rel="self" type="application/rss+xml" />
		<title>Newsconomy: Items tagged with "debugging"</title>
<link>http://newsconomy.com/tag/debugging</link>
<description>Recent items</description>
<pubDate>Thu, 08 Jan 2009 11:46:35 GMT</pubDate>
<language>en-us</language>
<webMaster>mudgen@gmail.com (Nick Mudge)</webMaster>
<item>
<title>PHP&#39;s debug_backtrace() Function</title>
<link>http://www.hudzilla.org/phpbook/read.php/19_8_8</link>
<pubDate>Tue, 11 Dec 2007 20:31:28 GMT</pubDate>
<description>It is all well and good to see the line where your code went wrong, but how did it get to that line? Debugging complex scripts can sometimes be a nightmare because objects call functions, which call other objects and other functions, and so on - you end up with a nest of calls that make tracing the problem difficult. To make your life easier, you can use the function debug_backtrace().</description>
<guid isPermaLink="false">http://newsconomy.com/item/126</guid>
</item>
<item>
<title>XRAY :: for web developers (bookmarklet with DOM inspector)</title>
<link>http://westciv.com/xray/</link>
<pubDate>Sun, 09 Dec 2007 18:50:39 GMT</pubDate>
<description></description>
<guid isPermaLink="false">http://newsconomy.com/item/117</guid>
</item>
</channel>
</rss>