FS#7880 - Valgrind crashes on startup with a illegal instruction error
Attached to Project:
Arch Linux
Opened by Qball Cow (qball) - Thursday, 23 August 2007, 10:19 GMT
Last edited by Eric Belanger (Snowman) - Friday, 24 August 2007, 06:34 GMT
Opened by Qball Cow (qball) - Thursday, 23 August 2007, 10:19 GMT
Last edited by Eric Belanger (Snowman) - Friday, 24 August 2007, 06:34 GMT
|
Details
Description:
If you start valgrind (either with memcheck or massif tool) it gives the following error: ==23485== Memcheck, a memory error detector. ==23485== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==23485== Using LibVEX rev 1732, a library for dynamic binary translation. ==23485== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==23485== Using valgrind-3.2.3, a dynamic binary instrumentation framework. ==23485== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==23485== For more details, rerun with: -v ==23485== vex amd64->IR: unhandled instruction bytes: 0x66 0x66 0x66 0x66 ==23485== valgrind: Unrecognised instruction at address 0x4014571. ==23485== Your program just tried to execute an instruction that Valgrind ==23485== did not recognise. There are two possible reasons for this. ==23485== 1. Your program has a bug and erroneously jumped to a non-code ==23485== location. If you are running Memcheck and you just saw a ==23485== warning about a bad jump, it's probably your program's fault. ==23485== 2. The instruction is legitimate but Valgrind doesn't handle it, ==23485== i.e. it's Valgrind's fault. If you think this is the case or ==23485== you are not sure, please let us know and we'll try to fix it. ==23485== Either way, Valgrind will now raise a SIGILL signal which will ==23485== probably kill your program. ==23485== ==23485== Process terminating with default action of signal 4 (SIGILL) ==23485== Illegal opcode at address 0x4014571 ==23485== at 0x4014571: memcpy (in /lib/ld-2.6.1.so) ==23485== by 0x40043AC: dl_main (in /lib/ld-2.6.1.so) ==23485== by 0x4012827: _dl_sysdep_start (in /lib/ld-2.6.1.so) ==23485== by 0x4001F20: _dl_start (in /lib/ld-2.6.1.so) ==23485== by 0x4000A67: (within /lib/ld-2.6.1.so) ==23485== ==23485== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==23485== malloc/free: in use at exit: 0 bytes in 0 blocks. ==23485== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. ==23485== For counts of detected errors, rerun with: -v ==23485== All heap blocks were freed -- no leaks are possible. Illegal instruction Additional info: * package version(s) valgrind 3.2.3-2 * config and/or log files etc. N/A Steps to reproduce: install valgrind run: valgrind true |
This task depends upon
Closed by Eric Belanger (Snowman)
Friday, 24 August 2007, 06:34 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in valgrind-3.2.3-2.1
Friday, 24 August 2007, 06:34 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in valgrind-3.2.3-2.1
==16546== Memcheck, a memory error detector.
==16546== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==16546== Using LibVEX rev 1732, a library for dynamic binary translation.
==16546== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==16546== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==16546== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==16546== For more details, rerun with: -v
==16546==
==16546==
==16546== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 1)
==16546== malloc/free: in use at exit: 0 bytes in 0 blocks.
==16546== malloc/free: 29 allocs, 29 frees, 2,205 bytes allocated.
==16546== For counts of detected errors, rerun with: -v
==16546== All heap blocks were freed -- no leaks are possible.
$ pacman -Q valgrind
valgrind 3.2.3-2
I don't seem to be able to reproduce this problem.
This bug looks specific to this arch.