On Mon, 12 Nov 2007, Bart Van Assche wrote: > Below you can find the contents of all writev.*.diff* files on my system > (for SVN revisions 7153 / 1793). I'm really puzzled by this -- any help in > solving this is certainly appreciated.
This is just one of those annoying cases where different systems give slightly different stack traces. We're already handling three different cases, but your system is slightly different again. Probably the best thing to do is add a .exp4 file. The other test cases that failed -- did they fail for similar reasons? How many of them failed? Nick > head -n 999 memcheck/tests/writev.*.diff* > ==> memcheck/tests/writev.stderr.diff <== > 3c3 > < at 0x........: writev (in /...libc...) > --- >> at 0x........: (within /...libc...) > 9c9 > < at 0x........: writev (in /...libc...) > --- >> at 0x........: (within /...libc...) > 15c15 > < at 0x........: readv (in /...libc...) > --- >> at 0x........: (within /...libc...) > > ==> memcheck/tests/writev.stderr.diff2 <== > 15c15 > < at 0x........: readv (in /...libc...) > --- >> at 0x........: (within /...libc...) > > ==> memcheck/tests/writev.stderr.diff3 <== > 3c3 > < at 0x........: do_writev (in /...libc...) > --- >> at 0x........: (within /...libc...) > 9c9 > < at 0x........: do_writev (in /...libc...) > --- >> at 0x........: (within /...libc...) > 15c15 > < at 0x........: do_readv (in /...libc...) > --- >> at 0x........: (within /...libc...) > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
