Skip to content

Instantly share code, notes, and snippets.

@Saurabh7
Created December 23, 2013 06:05
Show Gist options
  • Save Saurabh7/8092342 to your computer and use it in GitHub Desktop.
Save Saurabh7/8092342 to your computer and use it in GitHub Desktop.
valgrind --leak-check=yes ./a
==4530== Memcheck, a memory error detector
==4530== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==4530== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==4530== Command: ./a
==4530==
vex amd64->IR: unhandled instruction bytes: 0xC5 0xF9 0x57 0xC0 0xE8 0x43 0x17 0xFF
==4530== valgrind: Unrecognised instruction at address 0x517cd84.
==4530== at 0x517CD84: _GLOBAL__sub_I_Math.cpp (Math.h:429)
==4530== by 0x400F305: call_init.part.0 (dl-init.c:85)
==4530== by 0x400F3DE: _dl_init (dl-init.c:52)
==4530== by 0x40016E9: ??? (in /lib/x86_64-linux-gnu/ld-2.15.so)
==4530== Your program just tried to execute an instruction that Valgrind
==4530== did not recognise. There are two possible reasons for this.
==4530== 1. Your program has a bug and erroneously jumped to a non-code
==4530== location. If you are running Memcheck and you just saw a
==4530== warning about a bad jump, it's probably your program's fault.
==4530== 2. The instruction is legitimate but Valgrind doesn't handle it,
==4530== i.e. it's Valgrind's fault. If you think this is the case or
==4530== you are not sure, please let us know and we'll try to fix it.
==4530== Either way, Valgrind will now raise a SIGILL signal which will
==4530== probably kill your program.
==4530==
==4530== Process terminating with default action of signal 4 (SIGILL)
==4530== Illegal opcode at address 0x517CD84
==4530== at 0x517CD84: _GLOBAL__sub_I_Math.cpp (Math.h:429)
==4530== by 0x400F305: call_init.part.0 (dl-init.c:85)
==4530== by 0x400F3DE: _dl_init (dl-init.c:52)
==4530== by 0x40016E9: ??? (in /lib/x86_64-linux-gnu/ld-2.15.so)
==4530==
==4530== HEAP SUMMARY:
==4530== in use at exit: 11,961 bytes in 16 blocks
==4530== total heap usage: 20 allocs, 4 frees, 20,101 bytes allocated
==4530==
==4530== LEAK SUMMARY:
==4530== definitely lost: 0 bytes in 0 blocks
==4530== indirectly lost: 0 bytes in 0 blocks
==4530== possibly lost: 0 bytes in 0 blocks
==4530== still reachable: 11,961 bytes in 16 blocks
==4530== suppressed: 0 bytes in 0 blocks
==4530== Reachable blocks (those to which a pointer was found) are not shown.
==4530== To see them, rerun with: --leak-check=full --show-reachable=yes
==4530==
==4530== For counts of detected and suppressed errors, rerun with: -v
==4530== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
Illegal instruction (core dumped)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment