|
From: Konstantine B. <kb...@co...> - 2013-02-23 01:02:59
|
Hi, 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 :) . I would appreciate if someone could enlighten me on how to get it that file written. Thank you. Konstantine |
|
From: Philippe W. <phi...@sk...> - 2013-02-23 10:40:14
|
On Fri, 2013-02-22 at 20:02 -0500, Konstantine Bogach wrote: > Hi, 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 :) . I would > appreciate if someone could enlighten me on how to get it that file > written. It works here ... (f12/x86) for e.g. valgrind --tool=massif sleep 100 (both while letting valgrind terminate normally, or terminating it with kill -TERM) Philippe |
|
From: Konstantine B. <kb...@co...> - 2013-02-27 17:38:27
|
On 2/23/2013 5:40 AM, Philippe Waroquiers wrote: > On Fri, 2013-02-22 at 20:02 -0500, Konstantine Bogach wrote: >> Hi, 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 :) . I would >> appreciate if someone could enlighten me on how to get it that file >> written. > > It works here ... (f12/x86) for e.g. > valgrind --tool=massif sleep 100 > > (both while letting valgrind terminate normally, or terminating it > with kill -TERM) > > Philippe Philippe, it works with "sleep" or "ls" but I does not work when I run my programm. Any help will be apreciated. Thank you. Konstantine |
|
From: John R. <jr...@bi...> - 2013-02-27 17:57:47
|
>>> 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.
--
|
|
From: Philippe W. <phi...@sk...> - 2013-02-28 23:39:33
|
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 |