test: Fix segv test

Signal can be either BUS or TERM.

Close #86
v0.4.4
Document t.deepEqual
v0.4.5
Require Node >=0.8
Fixed warning about path.existsSync
Add --debug and --debug-brk to runner

--debug      Pass the '--debug' flag to node for debugging
--debug-brk  Pass the '--debug-brk' flag to node for debugging

e.g.
$ tap --debug-brk test/foo.js
debugger listening on port 5858

You then fire up node-inspector and debug like a boss..
Readme: fix parameter typo in usage with cover.
add harmony & strict command-line flags
v0.4.6
lib: don't assume 'node' is on the path

Use process.execPath to start the test runner.  Assuming there is a
node binary on the path somewhere will break when there isn't one or
when it's the wrong version.
v0.4.7
fix; command field in tap output not valid

Currently this fails:

not ok 1 test/settings/settings-test.js
  ---
    exit:     143
    timedOut: true
    command:  "node" "settings-test.js"
  ...

Because it cannot parse the "command" value, relevant yaml parsing error is:

  "expected <block end>, but found Scalar".

This fix changes the command value to be one quoted string instead which is
valid:

not ok 1 test/settings/settings-test.js
  ---
    exit:     143
    timedOut: true
    command:  "node settings-test.js"
  ...

Tests were ran against [InstantTap](http://instanttap.appspot.com/)
v0.4.8