|
From: Dennis L. <pla...@in...> - 2005-12-05 19:43:25
|
Hi, I noticed that the new tools all themselves include a main() function which just outputs: valgrind: You cannot run 'toolname' directly. valgrind: You should use $prefix/bin/valgrind. when it detects that the environment variable VALGRIND_LAUNCHER is not the correct one. Could one make it so that launching the "memcheck" program launches memcheck (so one can do "memcheck ls")? I have simply commented out the check for this environment variable beeing unset, and it seems to work ! Dunno if its the right way though... greets Dennis Carpe quod tibi datum est |
|
From: Julian S. <js...@ac...> - 2005-12-05 19:47:50
|
> I have simply commented out the check for this environment variable > beeing unset, Why? What problem does it solve? > Dunno if its the right way though... No. It is important for the valgrind launcher to be involved, for more than one reason. J |
|
From: Dennis L. <pla...@in...> - 2005-12-05 20:13:02
|
At 20:47 05.12.2005, Julian Seward wrote: >Why? What problem does it solve? It seems to let me start "memcheck ls" with the memcheck binary. > > Dunno if its the right way though... > >No. It is important for the valgrind launcher to be involved, for >more than one reason. Ok, I will then put some wrapperscripts to start it properly. The reason why "memcheck ls" is much easier for me than "valgrind --tool=memcheck ls" is that Im currently working with some wearable hardware that uses a heavily reconfigured variant of the frogpad (http://www.onehandedkeyboard.com/imagesfolder/frogrightjpg.JPG) where - and = are not so easy to reach ;) Could the program maybe exec "valgrind --tool=<whatevertool>" ? greets Dennis Carpe quod tibi datum est |
|
From: Nicholas N. <nj...@cs...> - 2005-12-05 20:17:50
|
On Mon, 5 Dec 2005, Dennis Lubert wrote: > The reason why "memcheck ls" is much easier for me than "valgrind > --tool=memcheck ls" is that Im currently working with some wearable > hardware that uses a heavily reconfigured variant of the frogpad > (http://www.onehandedkeyboard.com/imagesfolder/frogrightjpg.JPG) where - > and = are not so easy to reach ;) Can't you just create an alias or a wrapper script? Nick |
|
From: Dennis L. <pla...@in...> - 2005-12-05 20:25:31
|
At 21:17 05.12.2005, Nicholas Nethercote wrote: >On Mon, 5 Dec 2005, Dennis Lubert wrote: > >>The reason why "memcheck ls" is much easier for me than "valgrind >>--tool=memcheck ls" is that Im currently working with some wearable >>hardware that uses a heavily reconfigured variant of the frogpad >>(http://www.onehandedkeyboard.com/imagesfolder/frogrightjpg.JPG) >>where - and = are not so easy to reach ;) > >Can't you just create an alias or a wrapper script? Thats what I tried to say with "Ok, I will then put some wrapperscripts to start it properly." But it seemed to me a general good idea to suggest it, since for me (knowing only a bit of valgrind) it seemed to be easily implemented. And as you know, most programmers are lazy and will like to not type "valgrind --tool=" ;) greets Dennis Carpe quod tibi datum est |