Download Valgrind Documentation
Transcript
NEWS but accurately preserved. * Client requests for telling valgrind about memory pools. Developer (cvs head) release 2.1.1 (12 March 2004) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2.1.1 contains some internal structural changes needed for V’s long-term future. These don’t affect end-users. Most notable user-visible changes are: * Greater isolation between Valgrind and the program being run, so the program is less likely to inadvertently kill Valgrind by doing wild writes. * Massif: a new space profiling tool. Try it! It’s cool, and it’ll tell you in detail where and when your C/C++ code is allocating heap. Draws pretty .ps pictures of memory use against time. A potentially powerful tool for making sense of your program’s space use. * Fixes for many bugs, including support for more SSE2/SSE3 instructions, various signal/syscall things, and various problems with debug info readers. * Support for glibc-2.3.3 based systems. We are now doing automatic overnight build-and-test runs on a variety of distros. As a result, we believe 2.1.1 builds and runs on: Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 1, SuSE 8.2, SuSE 9. The following bugs, and probably many more, have been fixed. These are listed at http://bugs.kde.org. Reporting a bug for valgrind in the http://bugs.kde.org is much more likely to get you a fix than mailing developers directly, so please continue to keep sending bugs there. 69616 69856 73892 73145 73902 68633 75099 76839 76762 76747 76223 75604 76416 75614 75787 glibc 2.3.2 w/NPTL is massively different than what valgrind expects I don’t know how to instrument MMXish stuff (Helgrind) valgrind segfaults starting with Objective-C debug info (fix for S-type stabs) Valgrind complains too much about close(<reserved fd>) Shadow memory allocation seems to fail on RedHat 8.0 VG_N_SEMAPHORES too low (V itself was leaking semaphores) impossible to trace multiprocess programs the ‘impossible’ happened: disInstr: INT but not 0x80 ! vg_to_ucode.c:3748 (dis_push_segreg): Assertion ‘sz == 4’ failed. cannot include valgrind.h in c++ program parsing B(3,10) gave NULL type => impossible happens shmdt handling problem Problems with gcc 3.4 snap 20040225 using -gstabs when building your programs the ‘impossible’ happened Patch for some CDROM ioctls CDORM_GET_MCN, CDROM_SEND_PACKET, 58