Bug 13638 - (meta) Bugs found by jsfunfuzz
Summary: (meta) Bugs found by jsfunfuzz
Status: RESOLVED DUPLICATE of bug 23089
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: https://bugzilla.mozilla.org/show_bug...
Keywords:
Depends on: 6985 10878 10880 13620 13621 13622 13623 14891 14892 14897 17012 17013 17018 17020 17027 17924 17925 17927 17929 17931 17932 17936 17939 17940 23049 23054 23062 23063 23078 23085 23089 52493 52501 52505 52514 52515 52516 52643 52672 52690
Blocks:
  Show dependency tree / graph
 
Reported: 2007-05-09 02:34 PDT by Jesse Ruderman
Modified: 2012-09-06 16:49 PDT (History)
7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Ruderman 2007-05-09 02:34:52 PDT 
https://bugzilla.mozilla.org/show_bug.cgi?id=349611 contains a fuzz-testing script that generates random JavaScript functions (some with syntax errors).  It tests compilation, decompilation, interpretation, and lots more :)

It's sorta designed for testing Spidermonkey (Mozilla's JavaScript engine), but it seems to work against WebKit with a few small tweaks.  So far, it has found six decompilation bugs in JavaScriptCore (see dependencies).

It hangs fairly often due to bug 6985 (cyclic __proto__).  I haven't run it long enough to be confident that it doesn't find crashes.
Comment 1 Eric Seidel (no email) 2007-05-09 03:58:32 PDT 
adding bug 6985 since it blocks using jsfunfuzz.
Comment 2 Cameron Zwarich (cpst) 2008-09-02 19:48:18 PDT 
I will happily close this bug now, but if new issues come up from jsfunfuzz it should be reopened.
Comment 3 Oliver Hunt 2011-01-14 17:35:32 PST 
Lets keep this live for tracking purposes
Comment 4 Gavin Barraclough 2012-09-06 16:49:38 PDT 
Only one tracked bug left, so this isn't particularly useful for tracking porpoises any more.

*** This bug has been marked as a duplicate of bug 23089 ***