|
From: Christian P. <tr...@ge...> - 2005-07-22 18:29:41
|
On Friday 22 July 2005 10:50, Julian Seward wrote: > The memcheck in 2.4.0 doesn't complain about reading at partially > valid and partially invalid addresses, precisely to avoid reporting > this kind of error, but I thought that was sloppy and removed that > behaviour when rewriting it for Valgrind 3. So, in the end, is this a bug in glibc then? Which would mean for me to use= an=20 alternative way to count null terminated strings. Or should ignore this=20 message and wait until valgrind 3 will suppress those messages? > It would help a lot if your /lib/ld-2.3.5.so had symbols, so that > V could possibly see it was calling strlen and reroute to a less > optimised version. That's the easiest part. gimme some time to re-emerge it ;-) > Symbols would also make it possible to write=20 > a decent suppression if Plan A failed. > > If you are a Gentoo insider .. please consider distributing non-stripped > /lib/ld-2.3.5.so as removing the symbols from it makes Valgrind's > life much more difficult. The same goes for glibc. glibc is not my special subject though, but I can talk to those who are ;) Regards, Christian Parpart. =2D-=20 20:25:39 up 121 days, 9:33, 2 users, load average: 1.66, 2.23, 2.76 |