<?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 for Dave Pacheco&#039;s Blog</title>
	<atom:link href="http://dtrace.org/blogs/dap/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://dtrace.org/blogs/dap</link>
	<description>On software and technology</description>
	<lastBuildDate>Wed, 16 May 2012 16:03:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Debugging RangeError from a core dump by dap</title>
		<link>http://dtrace.org/blogs/dap/2012/05/14/debugging-rangeerror-from-a-core-dump/#comment-573</link>
		<dc:creator>dap</dc:creator>
		<pubDate>Wed, 16 May 2012 16:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=1069#comment-573</guid>
		<description>Geoff: That&#039;s a good thought.  In fact, Robert Mustacchi added process.abort() in Node 0.7.  It just calls the underlying abort(3C), which will usually cause your program to dump core.  The trick is calling it from somewhere where you still have enough context to debug what&#039;s going on -- ideally, where an exception is thrown.</description>
		<content:encoded><![CDATA[<p>Geoff: That&#8217;s a good thought.  In fact, Robert Mustacchi added process.abort() in Node 0.7.  It just calls the underlying abort(3C), which will usually cause your program to dump core.  The trick is calling it from somewhere where you still have enough context to debug what&#8217;s going on &#8212; ideally, where an exception is thrown.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging RangeError from a core dump by Geoff Flarity</title>
		<link>http://dtrace.org/blogs/dap/2012/05/14/debugging-rangeerror-from-a-core-dump/#comment-572</link>
		<dc:creator>Geoff Flarity</dc:creator>
		<pubDate>Wed, 16 May 2012 14:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=1069#comment-572</guid>
		<description>Awesome. It would be great if there was something like process.abort we could call. I&#039;m sure eventually we&#039;ll see this sort of debugging functionality outside of mdb/illumos land.</description>
		<content:encoded><![CDATA[<p>Awesome. It would be great if there was something like process.abort we could call. I&#8217;m sure eventually we&#8217;ll see this sort of debugging functionality outside of mdb/illumos land.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Profiling Node.js by Pie in the Sky (May 11, 2012) &#124; MSDN Blogs</title>
		<link>http://dtrace.org/blogs/dap/2012/04/25/profiling-node-js/#comment-555</link>
		<dc:creator>Pie in the Sky (May 11, 2012) &#124; MSDN Blogs</dc:creator>
		<pubDate>Fri, 11 May 2012 17:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=1027#comment-555</guid>
		<description>[...] Profiling Node.js: Dave Pacheoco walks through using DTrace and node-stackvis to figure out where your program is spending all it&#8217;s time. [...]</description>
		<content:encoded><![CDATA[<p>[...] Profiling Node.js: Dave Pacheoco walks through using DTrace and node-stackvis to figure out where your program is spending all it&rsquo;s time. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Profiling Node.js by Node.js - Techniques &#124; Pearltrees</title>
		<link>http://dtrace.org/blogs/dap/2012/04/25/profiling-node-js/#comment-457</link>
		<dc:creator>Node.js - Techniques &#124; Pearltrees</dc:creator>
		<pubDate>Thu, 26 Apr 2012 08:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=1027#comment-457</guid>
		<description>[...] (For returning readers, this is basically a “tl;dr” version of my previous post on Node.js performance .  Dave Pacheco&#039;s Blog » Profiling Node.js [...]</description>
		<content:encoded><![CDATA[<p>[...] (For returning readers, this is basically a “tl;dr” version of my previous post on Node.js performance .  Dave Pacheco&#039;s Blog » Profiling Node.js [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Profiling Node.js by Brendan Gregg</title>
		<link>http://dtrace.org/blogs/dap/2012/04/25/profiling-node-js/#comment-454</link>
		<dc:creator>Brendan Gregg</dc:creator>
		<pubDate>Wed, 25 Apr 2012 21:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=1027#comment-454</guid>
		<description>Nice!

If people are using this, I&#039;d recommend keeping either the folded-stack file or the original stack file (which is larger but more detailed), so that they can be reprocessed as we develop the flame graph software further (via either the node.js or Perl versions).</description>
		<content:encoded><![CDATA[<p>Nice!</p>
<p>If people are using this, I&#8217;d recommend keeping either the folded-stack file or the original stack file (which is larger but more detailed), so that they can be reprocessed as we develop the flame graph software further (via either the node.js or Perl versions).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Where does your Node program spend its time? by Dadypsuspilla</title>
		<link>http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/#comment-221</link>
		<dc:creator>Dadypsuspilla</dc:creator>
		<pubDate>Sun, 22 Jan 2012 02:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=643#comment-221</guid>
		<description>Hello! Just want to say thank you for this interesting article! =) Peace, Joy.</description>
		<content:encoded><![CDATA[<p>Hello! Just want to say thank you for this interesting article! =) Peace, Joy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Where does your Node program spend its time? by Brendan&#039;s blog &#187; Flame Graphs</title>
		<link>http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/#comment-204</link>
		<dc:creator>Brendan&#039;s blog &#187; Flame Graphs</dc:creator>
		<pubDate>Thu, 12 Jan 2012 23:37:26 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=643#comment-204</guid>
		<description>[...] post, Alan Coopersmith generated flame graphs of the X server, and Dave Pacheco created them with node.js functions.  Posted on December 16, 2011 at 10:24 am by Brendan Gregg · Permalink  [...]</description>
		<content:encoded><![CDATA[<p>[...] post, Alan Coopersmith generated flame graphs of the X server, and Dave Pacheco created them with node.js functions.  Posted on December 16, 2011 at 10:24 am by Brendan Gregg · Permalink  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Where does your Node program spend its time? by Where Does Your Node Program Spend Its Time? &#171; Joyeur</title>
		<link>http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/#comment-194</link>
		<dc:creator>Where Does Your Node Program Spend Its Time? &#171; Joyeur</dc:creator>
		<pubDate>Fri, 06 Jan 2012 19:29:50 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=643#comment-194</guid>
		<description>[...] Originally posted at Dave Pacheco&#8217;s Blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] Originally posted at Dave Pacheco&#8217;s Blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Where does your Node program spend its time? by Adam Leventhal</title>
		<link>http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/#comment-193</link>
		<dc:creator>Adam Leventhal</dc:creator>
		<pubDate>Thu, 05 Jan 2012 23:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=643#comment-193</guid>
		<description>hotness.</description>
		<content:encoded><![CDATA[<p>hotness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on USDT Providers Redux by dap</title>
		<link>http://dtrace.org/blogs/dap/2011/12/13/usdt-providers-redux/#comment-189</link>
		<dc:creator>dap</dc:creator>
		<pubDate>Sun, 18 Dec 2011 20:56:49 +0000</pubDate>
		<guid isPermaLink="false">http://dtrace.org/blogs/dap/?p=547#comment-189</guid>
		<description>Thanks, Richard!</description>
		<content:encoded><![CDATA[<p>Thanks, Richard!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

