Skip to content

Instantly share code, notes, and snippets.

@ericwomer
Created August 23, 2014 16:00
Show Gist options
  • Save ericwomer/4aa912110c14a4164e05 to your computer and use it in GitHub Desktop.
Save ericwomer/4aa912110c14a4164e05 to your computer and use it in GitHub Desktop.
==17509== Memcheck, a memory error detector
==17509== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==17509== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==17509== Command: /usr/bin/bashbug
==17509==
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xCE 0x3 0x1D 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==17509== valgrind: Unrecognised instruction at address 0x40113b6.
==17509== at 0x40113B6: _dl_allocate_tls_storage (in /lib64/ld-2.19.so)
==17509== by 0x40010CA: init_tls (in /lib64/ld-2.19.so)
==17509== by 0x4003458: dl_main (in /lib64/ld-2.19.so)
==17509== by 0x401513B: _dl_sysdep_start (in /lib64/ld-2.19.so)
==17509== by 0x4004AD3: _dl_start (in /lib64/ld-2.19.so)
==17509== by 0x40012D7: ??? (in /lib64/ld-2.19.so)
==17509== by 0x2: ???
==17509== by 0xFFEFFFD02: ???
==17509== by 0xFFEFFFD0A: ???
==17509== by 0xFFEFFFD0C: ???
==17509== Your program just tried to execute an instruction that Valgrind
==17509== did not recognise. There are two possible reasons for this.
==17509== 1. Your program has a bug and erroneously jumped to a non-code
==17509== location. If you are running Memcheck and you just saw a
==17509== warning about a bad jump, it's probably your program's fault.
==17509== 2. The instruction is legitimate but Valgrind doesn't handle it,
==17509== i.e. it's Valgrind's fault. If you think this is the case or
==17509== you are not sure, please let us know and we'll try to fix it.
==17509== Either way, Valgrind will now raise a SIGILL signal which will
==17509== probably kill your program.
==17509==
==17509== Process terminating with default action of signal 4 (SIGILL)
==17509== Illegal opcode at address 0x40113B6
==17509== at 0x40113B6: _dl_allocate_tls_storage (in /lib64/ld-2.19.so)
==17509== by 0x40010CA: init_tls (in /lib64/ld-2.19.so)
==17509== by 0x4003458: dl_main (in /lib64/ld-2.19.so)
==17509== by 0x401513B: _dl_sysdep_start (in /lib64/ld-2.19.so)
==17509== by 0x4004AD3: _dl_start (in /lib64/ld-2.19.so)
==17509== by 0x40012D7: ??? (in /lib64/ld-2.19.so)
==17509== by 0x2: ???
==17509== by 0xFFEFFFD02: ???
==17509== by 0xFFEFFFD0A: ???
==17509== by 0xFFEFFFD0C: ???
==17509== Jump to the invalid address stated on the next line
==17509== at 0x626: ???
==17509== Address 0x626 is not stack'd, malloc'd or (recently) free'd
==17509==
==17509==
==17509== Process terminating with default action of signal 11 (SIGSEGV)
==17509== Bad permissions for mapped region at address 0x626
==17509== at 0x626: ???
==17509==
==17509== HEAP SUMMARY:
==17509== in use at exit: 0 bytes in 0 blocks
==17509== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==17509==
==17509== All heap blocks were freed -- no leaks are possible
==17509==
==17509== For counts of detected and suppressed errors, rerun with: -v
==17509== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)
Segmentation fault
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment