|
From: Bauernberger, J. \(EXT\) <joa...@si...> - 2005-08-10 17:54:53
|
Hi, we have some very large apps which load massive amount of shared libs. After trying valgrind on one of them (app has around 10-20 child processes) I noticed that the logfile for the child does not get written. Instead I have all messages appear in the parents log (the PID does get appended to the file).=20 Also I just tried running some sample code that forks 5 children does some stuff and exits (see attached file). I ran this then using: valgrind --trace-children=3Dyes --log-file=3Dfoo ./fork I would have expected valgrind to make an individual logfile for every child. I checked the NEWS file (and archives) on that.=20 The NEWS file says - Small changes in control log file naming which make it easier to use valgrind for debugging MPI-based programs. The relevant new flags are --log-file-exactly=3D and --log-file-qualifier=3D. what are those 2 new flags for? The man page says to the --log-file=3D option: ... the file name used is created by concatenating the text filename, ".pid" and the process ID, so as to create a file per process.=20 should this still apply? thanks & best regards, joachim |