|
From: Juan C. M. S. <jua...@gm...> - 2010-06-24 20:05:25
|
Hello everybody, I am using the option --trace-mem=yes, but it looks like this is not a good option. Is the User Manual out of date? There is an alternative option for that? Thanks in advance. ***************** $ valgrind --tool=lackey --trace-mem=yes ./dijkstra_large input.dat > output_large.dat valgrind: Bad option '--trace-mem=yes'; aborting. valgrind: Use --help for more information. ***************** -- Juan Carlos |
|
From: Nicholas N. <n.n...@gm...> - 2010-06-25 06:36:11
|
On Thu, Jun 24, 2010 at 1:05 PM, Juan Carlos Martinez Santos > > I am using the option --trace-mem=yes, but it looks like this is not a > good option. Is the User Manual out of date? There is an alternative > option for that? > > Thanks in advance. > > ***************** > $ valgrind --tool=lackey --trace-mem=yes ./dijkstra_large input.dat > > output_large.dat > valgrind: Bad option '--trace-mem=yes'; aborting. > valgrind: Use --help for more information. > ***************** I just tried it and it worked for me. Which version of Valgrind are you using? 3.5.0 is the most recent. Nick |
|
From: Juan C. M. S. <jua...@gm...> - 2010-06-25 14:07:30
|
Sorry for the noise. Thanks Nicholas, I found that my path was wrong. Regards, Juan Carlos On Fri, Jun 25, 2010 at 2:35 AM, Nicholas Nethercote <n.n...@gm...> wrote: > On Thu, Jun 24, 2010 at 1:05 PM, Juan Carlos Martinez Santos >> >> I am using the option --trace-mem=yes, but it looks like this is not a >> good option. Is the User Manual out of date? There is an alternative >> option for that? >> >> Thanks in advance. >> >> ***************** >> $ valgrind --tool=lackey --trace-mem=yes ./dijkstra_large input.dat > >> output_large.dat >> valgrind: Bad option '--trace-mem=yes'; aborting. >> valgrind: Use --help for more information. >> ***************** > > I just tried it and it worked for me. Which version of Valgrind are > you using? 3.5.0 is the most recent. > > Nick > -- Juan Carlos |