Your message dated Thu, 23 Aug 2007 23:32:07 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#437503: fixed in valgrind 1:3.2.3-3 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: valgrind Version: 1:3.2.3-1 Architecture: amd64 $ cat t.c #include <stdio.h> int main() { printf("Hello World!\n"); return 0; } I compiled things static for a little more diagnostics, i.e. function names below. Basically same results with a dynamic binary. E.g. "valgrind ls" $ cc -Wall -O2 -g -static t.c -o t $ ./t Hello World! $ valgrind ./t ==19908== Memcheck, a memory error detector. ==19908== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==19908== Using LibVEX rev 1732, a library for dynamic binary translation. ==19908== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==19908== Using valgrind-3.2.3-Debian, a dynamic binary instrumentation framework. ==19908== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==19908== For more details, rerun with: -v ==19908== vex amd64->IR: unhandled instruction bytes: 0x66 0x66 0x66 0x66 ==19908== valgrind: Unrecognised instruction at address 0x451E22. ==19908== Your program just tried to execute an instruction that Valgrind ==19908== did not recognise. There are two possible reasons for this. ==19908== 1. Your program has a bug and erroneously jumped to a non-code ==19908== location. If you are running Memcheck and you just saw a ==19908== warning about a bad jump, it's probably your program's fault. ==19908== 2. The instruction is legitimate but Valgrind doesn't handle it, ==19908== i.e. it's Valgrind's fault. If you think this is the case or ==19908== you are not sure, please let us know and we'll try to fix it. ==19908== Either way, Valgrind will now raise a SIGILL signal which will ==19908== probably kill your program. ==19908== ==19908== Process terminating with default action of signal 4 (SIGILL) ==19908== Illegal opcode at address 0x451E22 ==19908== at 0x451E22: strpbrk (in /p/IM/t) ==19908== by 0x448429: strsep (in /p/IM/t) ==19908== by 0x42CAB0: fillin_rpath (in /p/IM/t) ==19908== by 0x42E8DB: _dl_init_paths (in /p/IM/t) ==19908== by 0x40DFCE: _dl_non_dynamic_init (in /p/IM/t) ==19908== by 0x40E6DA: __libc_init_first (in /p/IM/t) ==19908== by 0x400423: (below main) (in /p/IM/t) ==19908== ==19908== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==19908== malloc/free: in use at exit: 0 bytes in 0 blocks. ==19908== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. ==19908== For counts of detected errors, rerun with: -v ==19908== All heap blocks were freed -- no leaks are possible. Illegal instruction
--- End Message ---
--- Begin Message ---Source: valgrind Source-Version: 1:3.2.3-3 We believe that the bug you reported is fixed in the latest version of valgrind, which is due to be installed in the Debian FTP archive: valgrind_3.2.3-3.diff.gz to pool/main/v/valgrind/valgrind_3.2.3-3.diff.gz valgrind_3.2.3-3.dsc to pool/main/v/valgrind/valgrind_3.2.3-3.dsc valgrind_3.2.3-3_amd64.deb to pool/main/v/valgrind/valgrind_3.2.3-3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrés Roldán <[EMAIL PROTECTED]> (supplier of updated valgrind package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 23 Aug 2007 22:41:13 +0000 Source: valgrind Binary: valgrind Architecture: source amd64 Version: 1:3.2.3-3 Distribution: unstable Urgency: low Maintainer: Andrés Roldán <[EMAIL PROTECTED]> Changed-By: Andrés Roldán <[EMAIL PROTECTED]> Description: valgrind - A memory debugger and profiler Closes: 424129 437503 Changes: valgrind (1:3.2.3-3) unstable; urgency=low . * debian/FAQ.txt: - Provided there to solve FTBFS if valgrind is built twice in a row (Closes: #424129) * debian/patches/01_amd64-nops.dpatch: - Patch to handle new way of writing NOPs by binutils. (Closes: #437503) * debian/patches/01_configure.dpatch: - Merged into 02_version.patch * debian/patches/03_valgrind-libc6-2.6.dpatch: - Took off from dpatch and merged into debian diff. Files: 241769f3efef50253214d335c3a65630 767 devel optional valgrind_3.2.3-3.dsc e46e9b16febfaaf06d0f057f95b15a47 148369 devel optional valgrind_3.2.3-3.diff.gz 16b67ecca6d1c8482256c3681f40a667 27336522 devel optional valgrind_3.2.3-3_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGzhem2OByS7KTlusRAi/ZAJ9LySlHoMfI2AeUdHNcC4FH6+j9UACg1iOp 9HxI+uy+X2Wo4GSPfA2DCXw= =Ko1F -----END PGP SIGNATURE-----
--- End Message ---
