Thanks for your reply,
On 16/02/19 17:08, Philippe Waroquiers wrote:
--undef-value-errors is not a massif option, it is a memcheck option.
I haven't specified that option at all! I don't know where it gets it
from. All I want is to get a memory profile of my program and the net
all over points to
valgrind --tool=massif executable
that's all.
So, it is completely normal that massif reports that this is an
unknown option.
If you want to have the list of options massif understands,
you have to do:
valgrind --tool=massif --help
If you do not specify a tool, then valgrind defaults to memcheck.
Note that you can also prefix options with the tool they are
aimed at.
So, e.g.
valgrind --tool=massif --memcheck:undef-value-errors=no executable
does not complain.
sorry but that fails with same error in my system
valgrind: Unknown option: --undef-value-errors=no
valgrind: Use --help for more information or consult the user manual.
Philippe
On Sat, 2019-02-16 at 15:20 +0200, / via Valgrind-users wrote:
Hi people, I get the following error when I try to invoke "massif" in
the most simple manner:
valgrind: Unknown option: --undef-value-errors=no
valgrind: Use --help for more information or consult the user manual.
Command to reproduce the error:
valgrind --verbose --tool=massif executable
where executable was the program i wanted to check (compiled with -g)
even a simple
valgrind --verbose --tool=massif /bin/bash
produces the same error
** Valgrind version:
valgrind-3.14.0
Fedora, linux 4.18.19-100
Many thanks,
a.
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
