From: Bart V. A. <bar...@gm...> - 2008-12-24 15:06:05
|
On Wed, Dec 24, 2008 at 2:31 PM, Madhan Sadasivam <mad...@gm...> wrote: > > Hello, > > I am using Valgrind-3.3.1, to test my multi-threaded application. > I am using the following options. > > --log-file=/scratch/valg/valgrind_agent.log%p > --leak-check=full > --leak-resolution=high > --show-reachable=yes > --track-fds=yes > --workaround-gcc296-bugs=yes > --error-limit=no > --num-callers=60 > --run-libc-freeres=no > -v > --tool=memcheck > > > The log file seems to have output mixed up from multiple pids. > For example here is a sample. The errors from processes 15155 and 15151 > are appearing at the same time and making the error message unusable. > > > ==15155== ==15151== by 0x805EE02: agent(int, unsigned char**) (Agent.cpp:153) > ==15151== by 0x8057790: main (AgentMain.cpp:125) > ==15155== > ====15151== > ==15151=14 bytes in 112 bytes in 1 blocks are still reachable in loss record 272 of 4,611===15151== > > > A major portion of the log file is clean, but after a certain time, everything > is mixed up. Will the xml option solve this issue. I don't know whether the XML option will solve this issue, but if I remember correctly, this issue was solved in r7875. Can you please test whether the above issue is solved in the trunk version of Valgrind ? You can find instructions for downloading and compiling the trunk on Valgrind's web page. Bart. |