|
From: Roger M. <ro...@qu...> - 2009-06-02 18:27:59
|
Hi developers, I've been having a productive time with massif; it is a very useful tool to have in my toolbox. Thank you. Thought it may help someone else if the documentation at: http://valgrind.org/docs/manual/ms-manual.html where it is talking about the -g flag, included a note about not applying a gcc build flag called -static. This flag apparently changes the resulting of the executable so that massif cannot find new, malloc, etc. ....... First off, as for the other Valgrind tools, you should compile with debugging info (the |-g| flag) . You can compile and link with static libraries but do not include -static flag during linking. ... ....... Something like that. If the -static flag is set, valgrind massif will not find any memory allocation routines and the output will be blank. Only the beginning nil snapshot and that's it. Remove the -static and massif works great. |