On Wed, Dec 24, 2008 at 11:17 PM, Nicholas Nethercote <[email protected]> wrote: > On Wed, 24 Dec 2008, Bart Van Assche wrote: > >>> 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== >> >> 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. > > I doubt that r7875 solves it -- without interprocess communication or file > locking, if two processes are trying to write to the same file you'll get a > jumble, no?
As far as I can see the original question is about a multithreaded application, not about multiple processes. r7875 buffers Valgrind's message output per line such that output written by different threads does not get mixed up. Bart. ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
