From: Konstantin S. <kon...@gm...> - 2009-06-02 19:23:55
|
On Tue, Jun 2, 2009 at 10:27 PM, Roger Martin <ro...@qu...> wrote: > 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. ... > ....... Such information could be found somewhere in the docs (though maybe not on the front page). What we really need, is a BIG WARNING when valgrind tools encounter static executable or lack of debug info. --kcc > 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. > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > |