<?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: Lessons from JS engine bugs</title>
	<atom:link href="http://www.squarefree.com/2011/09/01/lessons-from-js-engine-bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.squarefree.com/2011/09/01/lessons-from-js-engine-bugs/</link>
	<description>Jesse Ruderman on Firefox, security, and more</description>
	<lastBuildDate>Fri, 02 Mar 2012 12:46:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Benjamin Otte</title>
		<link>http://www.squarefree.com/2011/09/01/lessons-from-js-engine-bugs/comment-page-1/#comment-12324</link>
		<dc:creator>Benjamin Otte</dc:creator>
		<pubDate>Fri, 02 Sep 2011 12:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/?p=791#comment-12324</guid>
		<description><![CDATA[About OOM fuzzing: The method that I have tried and found to be reasonably fast is to fork(), return NULL in the child and see if it terminates properly. The parent would continue without failures. (I wrote that up in http://blogs.gnome.org/otte/2007/11/03/robustness-testing/ but the links from there are all gone.) IIRC that method was something like 30x slower than normal execution of the program, but it at least was essentially O(runtime of original program).
Also, it gets tricky when your code writes to files/sockets, but for a JS engine you should be able to avoid that.]]></description>
		<content:encoded><![CDATA[<p>About OOM fuzzing: The method that I have tried and found to be reasonably fast is to fork(), return NULL in the child and see if it terminates properly. The parent would continue without failures. (I wrote that up in <a href="http://blogs.gnome.org/otte/2007/11/03/robustness-testing/" rel="nofollow">http://blogs.gnome.org/otte/2007/11/03/robustness-testing/</a> but the links from there are all gone.) IIRC that method was something like 30x slower than normal execution of the program, but it at least was essentially O(runtime of original program).<br />
Also, it gets tricky when your code writes to files/sockets, but for a JS engine you should be able to avoid that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
