|
From: Julian S. <js...@ac...> - 2003-12-14 18:23:53
|
2.1.0 is available at the usual place, http://valgrind.kde.org. J Unstable (cvs head) release 2.1.0 (15 December 2003) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For whatever it's worth, 2.1.0 actually seems pretty darn stable to me (Julian). It looks eminently usable, and given that it fixes some significant bugs, may well be worth using on a day-to-day basis. 2.1.0 is known to build and pass regression tests on: SuSE 9, SuSE 8.2, RedHat 8. 2.1.0 most notably includes Jeremy Fitzhardinge's complete overhaul of handling of system calls and signals, and their interaction with threads. In general, the accuracy of the system call, thread and signal simulations is much improved. Specifically: - Blocking system calls behave exactly as they do when running natively (not on valgrind). That is, if a syscall blocks only the calling thread when running natively, than it behaves the same on valgrind. No more mysterious hangs because V doesn't know that some syscall or other, should block only the calling thread. - Interrupted syscalls should now give more faithful results. - Finally, signal contexts in signal handlers are supported. As a result, konqueror on SuSE 9 no longer segfaults when notified of file changes in directories it is watching. Other changes: - Robert Walsh's file descriptor leakage checks. When enabled, Valgrind will print out a list of open file descriptors on exit. Along with each file descriptor, Valgrind prints out a stack backtrace of where the file was opened and any details relating to the file descriptor such as the file name or socket details. To use, give: --track-fds=yes - Implemented a few more SSE/SSE2 instructions. - Less crud on the stack when you do 'where' inside a GDB attach. - Fixed the following bugs: 68360: Valgrind does not compile against 2.6.0-testX kernels 68525: CVS head doesn't compile on C90 compilers 68566: pkgconfig support (wishlist) 68588: Assertion `sz == 4' failed in vg_to_ucode.c (disInstr) 69140: valgrind not able to explicitly specify a path to a binary. 69432: helgrind asserts encountering a MutexErr when there are EraserErr suppressions - Increase the max size of the translation cache from 200k average bbs to 300k average bbs. Programs on the size of OOo (680m17) are thrashing the cache at the smaller size, creating large numbers of retranslations and wasting significant time as a result. |