|
From: Bauernberger, J. \(EXT\) <joa...@si...> - 2005-08-10 13:22:24
|
Hi there,
$ valgrind --tool=3Daddrcheck ls
Can't open tool "addrcheck":
/opt/valgrind/valgrind-3.0.0/lib/valgrind/vgtool_addrcheck.so: cannot
open shared object file: No such file or directory
valgrind: couldn't load tool
Available tools:
cachegrind
helgrind
lackey
massif
memcheck
none
on the other hand memcheck works now even on huge targets where valgrind
told me to use addrcheck in earlier version=20
i did :
configure --enable-tls --prefix=3D/opt/valgrind/valgrind-3.0.0 && make =
&&
make install
lib/> ls -l=20
-r--r--r-- 1 xxx xxx 16809 Aug 10 14:32 default.supp
-r--r--r-- 1 xxx xxx 9338 Aug 10 14:33 glibc-2.2.supp
-r--r--r-- 1 xxx xxx 9702 Aug 10 14:33 glibc-2.3.supp
-r--r--r-- 1 xxx xxx 727 Aug 10 14:33 glibc-2.4.supp
-r-xr-xr-x 1 xxx xxx 84362 Aug 10 14:33 hp2ps
-r-xr-xr-x 1 xxx xxx 2210949 Aug 10 14:33 stage2
-r-xr-xr-x 1 xxx xxx 7544 Aug 10 14:33 vg_preload_core.so
-r-xr-xr-x 1 xxx xxx 28959 Aug 10 14:33 vgpreload_helgrind.so
-r-xr-xr-x 1 xxx xxx 28959 Aug 10 14:33 vgpreload_massif.so
-r-xr-xr-x 1 xxx xxx 44402 Aug 10 14:33 vgpreload_memcheck.so
-r-xr-xr-x 1 xxx xxx 61766 Aug 10 14:33 vgtool_cachegrind.so
-r-xr-xr-x 1 xxx xxx 77463 Aug 10 14:33 vgtool_helgrind.so
-r-xr-xr-x 1 xxx xxx 24055 Aug 10 14:33 vgtool_lackey.so
-r-xr-xr-x 1 xxx xxx 60639 Aug 10 14:33 vgtool_massif.so
-r-xr-xr-x 1 xxx xxx 203276 Aug 10 14:33 vgtool_memcheck.so
-r-xr-xr-x 1 xxx xxx 18884 Aug 10 14:33 vgtool_none.so
-r--r--r-- 1 xxx xxx 3107 Aug 10 14:33 xfree-3.supp
-r--r--r-- 1 xxx xxx 3873 Aug 10 14:33 xfree-4.supp
any ideas?
thanks,
joachim
|
|
From: Nicholas N. <nj...@cs...> - 2005-08-10 13:30:09
|
On Wed, 10 Aug 2005, Bauernberger, Joachim (EXT) wrote: > $ valgrind --tool=addrcheck ls > Can't open tool "addrcheck": From the NEWS file: - Addrcheck is currently not working. We hope to get it working again soon. Helgrind is still not working, as was the case for the 2.4.0 release. Is there a problem with reading the NEWS file? This is about the 5th time someone has asked about Addrcheck or Helgrind. I don't want to put this info in the FAQ because it seems like having it in the NEWS should be enough. N |
|
From: Bob R. <bo...@br...> - 2005-08-10 13:36:14
|
On Wed, Aug 10, 2005 at 08:30:03AM -0500, Nicholas Nethercote wrote: > On Wed, 10 Aug 2005, Bauernberger, Joachim (EXT) wrote: > > >$ valgrind --tool=addrcheck ls > >Can't open tool "addrcheck": > > >From the NEWS file: > > - Addrcheck is currently not working. We hope to get it working again > soon. Helgrind is still not working, as was the case for the 2.4.0 > release. > > Is there a problem with reading the NEWS file? This is about the 5th time > someone has asked about Addrcheck or Helgrind. I don't want to put this > info in the FAQ because it seems like having it in the NEWS should be > enough. I think it would make sense to post this kind of info in the manual. I mean, the first thing a user does is read the 3.0 manual and find out that a nifty plugin called Addrcheck is there. Then when they go to use it, it doesn't work. So they naturally ask here. What would point them to reading the NEWS file? As I understand it, valgrind is special in the sense that most programs don't "pick up/drop" support for plugins between versions. Usually once a program supports a feature set, it doesn't go back. Bob Rossi |
|
From: Avery P. <ape...@ni...> - 2005-08-10 13:46:03
|
On Wed, Aug 10, 2005 at 08:30:03AM -0500, Nicholas Nethercote wrote: > On Wed, 10 Aug 2005, Bauernberger, Joachim (EXT) wrote: > > >$ valgrind --tool=addrcheck ls > >Can't open tool "addrcheck": > > From the NEWS file: > > - Addrcheck is currently not working. We hope to get it working again > soon. Helgrind is still not working, as was the case for the 2.4.0 > release. > > Is there a problem with reading the NEWS file? This is about the 5th time > someone has asked about Addrcheck or Helgrind. I don't want to put this > info in the FAQ because it seems like having it in the NEWS should be > enough. People don't read documentation. Why not create a temporary addrcheck plugin that just says, "Sorry, addrcheck is not yet supported in valgrind 3.0.0. If you need it, use an earlier version" and then aborts? You can guarantee that should make the questions go away (at least, the questions will then be, "So when is it coming back?") Have fun, Avery |
|
From: Nicholas N. <nj...@cs...> - 2005-08-10 13:51:47
|
On Wed, 10 Aug 2005, Avery Pennarun wrote: > People don't read documentation. Why not create a temporary addrcheck > plugin that just says, "Sorry, addrcheck is not yet supported in valgrind > 3.0.0. If you need it, use an earlier version" and then aborts? Ah, that's a good idea. N |
|
From: Bob R. <bo...@br...> - 2005-08-10 15:38:33
|
On Wed, Aug 10, 2005 at 08:51:40AM -0500, Nicholas Nethercote wrote: > On Wed, 10 Aug 2005, Avery Pennarun wrote: > > >People don't read documentation. Why not create a temporary addrcheck > >plugin that just says, "Sorry, addrcheck is not yet supported in valgrind > >3.0.0. If you need it, use an earlier version" and then aborts? > > Ah, that's a good idea. Yes, this idea makes the most sense and is very practical. The only questions you might get then is, why isn't this supported? So, maybe a small reason why would also be helpful enough to keep away questions regarding this issue. Bob Rossi |
|
From: Nicholas N. <nj...@cs...> - 2005-08-10 16:09:30
|
On Wed, 10 Aug 2005, Bob Rossi wrote: >>> People don't read documentation. Why not create a temporary addrcheck >>> plugin that just says, "Sorry, addrcheck is not yet supported in valgrind >>> 3.0.0. If you need it, use an earlier version" and then aborts? >> >> Ah, that's a good idea. > > Yes, this idea makes the most sense and is very practical. The only > questions you might get then is, why isn't this supported? So, maybe a > small reason why would also be helpful enough to keep away questions > regarding this issue. Yep. N |
|
From: Avery P. <ape...@ni...> - 2005-08-10 16:22:26
|
On Wed, Aug 10, 2005 at 11:38:21AM -0400, Bob Rossi wrote: > On Wed, Aug 10, 2005 at 08:51:40AM -0500, Nicholas Nethercote wrote: > > On Wed, 10 Aug 2005, Avery Pennarun wrote: > > > > >People don't read documentation. Why not create a temporary addrcheck > > >plugin that just says, "Sorry, addrcheck is not yet supported in valgrind > > >3.0.0. If you need it, use an earlier version" and then aborts? > > > > Ah, that's a good idea. > > Yes, this idea makes the most sense and is very practical. The only > questions you might get then is, why isn't this supported? So, maybe a > small reason why would also be helpful enough to keep away questions > regarding this issue. ...or perhaps we could rephrase: "Sorry, addrcheck is not yet supported in valgrind 3. See the NEWS file." Once you've actually smacked them in the head with it, they might actually read the documentation :) Have fun, Avery |
|
From: Tom H. <to...@co...> - 2005-08-10 13:32:41
|
In message <21B78378E540EC4795820EFF451D857F199FF7@MCHP7I5A.ww002.siemens.net>
Joachim Bauernberger <joa...@si...> wrote:
> $ valgrind --tool=addrcheck ls
> Can't open tool "addrcheck":
> /opt/valgrind/valgrind-3.0.0/lib/valgrind/vgtool_addrcheck.so: cannot
> open shared object file: No such file or directory
> valgrind: couldn't load tool
Please read the release announcement (or the NEWS file, or the many
previous enquiries on this list) for more information on this subject.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|