On Wed, 2013-02-27 at 09:58 -0800, John Reiser wrote: > >>> I am on 3.8.1 now and I can not get massif to produce an output > >>> file, neither default name nor specifying it on command line. I > >>> terminate my program by sending TERM signal to valgrind process. That > >>> worked on 3.4.1 (yes, I don't use valgrind oftern :) > [snip] > > > it works with "sleep" or "ls" but I does not work when I > > run my programm. > > Run valgrind under strace and inspect all file operations: > > strace -f -o strace.out -e trace=file,close,dup,dup2 \ > valgrind <options> ./my_app <args> > > Look for an extra close(), etc. You can also start valgrind with some additional tracing options and compare the difference between a kill -TERM of a sleep 1000 under Valgrind and a kill -TERM of your application.
for example, do: valgrind --tool=massif -v -v -v -d -d -d --trace-signals=yes sleep 1000 Maybe this gives some light about what goes wrong ... Philippe ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
