|
From: franchouze <f_c...@ya...> - 2006-07-05 14:05:07
|
Hi Here is my valgrind command line : valgrind --tool=memcheck --trace-children=yes --track-fds=yes --leak-check=full --show-reachable=yes --log-file=debug --num-callers=16 prog/args the program runs normally and create logfiles and then I got a core dumped and this message : ==10940== Can't create log file 'debug.10940' (Permission denied); giving up! valgrind: Bad option '--log-file=<file> (didn't work out for some reason.)'; aborting. valgrind: Use --help for more information. ==10941== Can't create log file 'debug.10941' (Permission denied); giving up! valgrind: Bad option '--log-file=<file> (didn't work out for some reason.)'; aborting. valgrind: Use --help for more information. I still have space on the hard drive and I have rights to write in the current directory (valgrind wrote some logfiles). Anyone has got an idea about the "some reason" that crashed the program ? Thanks for your help Fran?ois -- View this message in context: http://www.nabble.com/valgrind-error-%3A--Can%27t-create-log-file-tf1894805.html#a5181944 Sent from the Valgrind - Users forum at Nabble.com. |
|
From: Julian S. <js...@ac...> - 2006-07-05 14:21:24
|
Your program changes working directory and then does fork/exec. The child valgrind cannot write a log file in the new directory. You can get round this by giving a fully qualified file name to --log-file=. J On Wednesday 05 July 2006 14:47, franchouze wrote: > Hi > > Here is my valgrind command line : > valgrind --tool=memcheck --trace-children=yes --track-fds=yes > --leak-check=full --show-reachable=yes --log-file=debug --num-callers=16 > prog/args > > the program runs normally and create logfiles and then I got a core dumped > and this message : > > ==10940== Can't create log file 'debug.10940' (Permission denied); giving > up! > valgrind: Bad option '--log-file=<file> (didn't work out for some > reason.)'; aborting. > valgrind: Use --help for more information. > ==10941== Can't create log file 'debug.10941' (Permission denied); giving > up! > valgrind: Bad option '--log-file=<file> (didn't work out for some > reason.)'; aborting. > valgrind: Use --help for more information. > > I still have space on the hard drive and I have rights to write in the > current directory (valgrind wrote some logfiles). > > Anyone has got an idea about the "some reason" that crashed the program ? > > Thanks for your help > > Fran?ois |
|
From: franchouze <f_c...@ya...> - 2006-07-05 15:34:30
|
You were right. Thanks a lot. Francois -- View this message in context: http://www.nabble.com/valgrind-error-%3A--Can%27t-create-log-file--solved--tf1894805.html#a5183969 Sent from the Valgrind - Users forum at Nabble.com. |