|
From: Julian S. <js...@ac...> - 2005-08-01 10:40:40
|
We are pleased to announce a new stable release of Valgrind, version 2.4.1. It is available from http://www.valgrind.org. Valgrind is an award-winning open-source suite of simulation based debugging and profiling tools. With the tools that come with Valgrind, you can automatically detect many memory management bugs, avoiding hours of frustrating bug-hunting, and make your code more stable. You can also perform detailed time and space profiling to help speed up and slim down your programs. 2.4.1 is a maintenance release that contains various bug fixes which have accumulated since 2.4.0 was released about four months ago. Details are below. 2.4.1 still only supports x86-linux. For amd64-linux support, please wait for 3.0, which will ship shortly. Many thanks to Dirk Mueller for coordinating the 2.4.1 release. Happy (and productive) debugging and profiling, -- The Valgrind developers New in 2.4.1 vs 2.4.0 ~~~~~~~~~~~~~~~~~~~~~ - fixed regression in stabs parsing introduced by fixing bug 90128 - major performance fix by Pete Moceyunas to improve malloc handling - several smaller fixes to the code, as detected in a code analysis performed by Madhu Kurup using the "Prevent" Stanford code checker - bug in VG_(atoll36) fixed -- this might have been causing some failures in C++ name demangling - fixed double free in reading ~/.valgrindrc - removed irrelevant linker version script that broke compilation with newer binutils. - fixes for the following bugs: 88678: fix debug info for file names containing spaces 106713: preserve %esi accross calls to clone. 103509: times(NULL) gets incorrect unaddressable bytes warning 106293: fix stack-scanning in VALGRIND_DO_LEAK_CHECK 104797: handle BLKGETSIZE64 ioctl 101881: segfault when command-line-args are in RO-memory - fix valgrind crash when no environment is given to an execve() call - disable PIE compilation by default. It caused too many non-working builds and accordingly many bugreports. - fix stabs debug info reading for FreePascal binaries - update syscall table to include new syscalls included in Linux 2.6.13. - updates to compile properly with gcc 4.x and glibc 2.4 New features: The macros VALGRIND_STACK_REGISTER, VALGRIND_STACK_DEREGISTER and VALGRIND_STACK_CHANGE have been added. These can be used to inform valgrind about stack switches, if your application uses userland threading libraries. |
|
From: Dennis L. <pla...@in...> - 2005-08-01 12:45:38
|
Looks like the SIOCGIFNAME bug mentioned a while ago on the list (and fixed in 3.x then) isnt yet fixed in this... Carpe quod tibi datum est |
|
From: Dirk M. <dm...@gm...> - 2005-08-01 20:44:36
|
On Monday 01 August 2005 14:45, Dennis Lubert wrote: > Looks like the SIOCGIFNAME bug mentioned a while ago on the list (and fixed > in 3.x then) isnt yet fixed in this... you know which change in particular is responsible for this? there is no hit for SIOCGIFNAME anywhere inside the valgrind-2.4 tree. |
|
From: Dennis L. <pla...@in...> - 2005-08-01 21:04:41
|
At 22:43 01.08.2005, Dirk Mueller wrote: >On Monday 01 August 2005 14:45, Dennis Lubert wrote: > > > Looks like the SIOCGIFNAME bug mentioned a while ago on the list (and fixed > > in 3.x then) isnt yet fixed in this... > >you know which change in particular is responsible for this? there is no hit >for SIOCGIFNAME anywhere inside the valgrind-2.4 tree. coregrind/vg_syscalls.c l. 3044 ff. There is some integer parameter to the ioctl which is the index of the interface, which is misinterpreted by valgrind as an address thus causing a false "inaccesible memory passed to ioctl" error by valgrind. (It was on the list just a while ago and fixed in 3.x tree) greets Dennis Carpe quod tibi datum est |