gistfile1.txt

[02:29 PM:node(v0.6)] $ valgrind ./node
==16941== Memcheck, a memory error detector
==16941== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==16941== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==16941== Command: ./node
==16941== 
--16941-- ./node:
--16941-- dSYM directory is missing; consider using --dsymutil=yes
vex amd64->IR: unhandled instruction bytes: 0xCF 0xFA 0xED 0xFE 0x7 0x0 0x0 0x1
==16941== valgrind: Unrecognised instruction at address 0x1000.
==16941==    at 0x1000: ??? (in /usr/local/Cellar/valgrind/3.7.0/lib/valgrind/vgpreload_core-amd64-darwin.so)
==16941==    by 0x100006035: node::Start(int, char**) (in ./node)
==16941==    by 0x100001893: (below main) (in ./node)
==16941== Your program just tried to execute an instruction that Valgrind
==16941== did not recognise.  There are two possible reasons for this.
==16941== 1. Your program has a bug and erroneously jumped to a non-code
==16941==    location.  If you are running Memcheck and you just saw a
==16941==    warning about a bad jump, it's probably your program's fault.
==16941== 2. The instruction is legitimate but Valgrind doesn't handle it,
==16941==    i.e. it's Valgrind's fault.  If you think this is the case or
==16941==    you are not sure, please let us know and we'll try to fix it.
==16941== Either way, Valgrind will now raise a SIGILL signal which will
==16941== probably kill your program.
==16941== 
==16941== Process terminating with default action of signal 4 (SIGILL)
==16941==  Illegal opcode at address 0x1000
==16941==    at 0x1000: ??? (in /usr/local/Cellar/valgrind/3.7.0/lib/valgrind/vgpreload_core-amd64-darwin.so)
==16941==    by 0x100006035: node::Start(int, char**) (in ./node)
==16941==    by 0x100001893: (below main) (in ./node)
==16941== 
==16941== HEAP SUMMARY:
==16941==     in use at exit: 361,540 bytes in 1,068 blocks
==16941==   total heap usage: 1,664 allocs, 596 frees, 519,716 bytes allocated
==16941== 
==16941== LEAK SUMMARY:
==16941==    definitely lost: 16 bytes in 1 blocks
==16941==    indirectly lost: 0 bytes in 0 blocks
==16941==      possibly lost: 0 bytes in 0 blocks
==16941==    still reachable: 361,524 bytes in 1,067 blocks
==16941==         suppressed: 0 bytes in 0 blocks
==16941== Rerun with --leak-check=full to see details of leaked memory
==16941== 
==16941== For counts of detected and suppressed errors, rerun with: -v
==16941== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 402 from 14)
Illegal instruction: 4