Comment # 36
on bug 12656
from Guy Harris
OK, we're down to
==16494== Memcheck, a memory error detector
==16494== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==16494== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==16494== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-16-30351.pcap
==16494==
==16494==
==16494== HEAP SUMMARY:
==16494== in use at exit: 2,038,967 bytes in 46,070 blocks
==16494== total heap usage: 417,163 allocs, 371,093 frees, 48,419,440 bytes
allocated
==16494==
==16494== LEAK SUMMARY:
==16494== definitely lost: 3,506 bytes in 154 blocks
==16494== indirectly lost: 405,690 bytes in 17,124 blocks
==16494== possibly lost: 0 bytes in 0 blocks
==16494== still reachable: 1,629,771 bytes in 28,792 blocks
==16494== suppressed: 0 bytes in 0 blocks
==16494== Rerun with --leak-check=full to see details of leaked memory
==16494==
==16494== For counts of detected and suppressed errors, rerun with: -v
==16494== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-16-30351.err
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-16-30351.pcap
sftp> put /fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-*
program finished with exit code 255
in the 2.2 buildbot.
That still doesn't explain why "ERROR SUMMARY: 0 errors from 0 contexts
(suppressed: 1 from 1)" is turning into an exit status of 255 - is that the
valground tshark, or sftp, or something else, that's exiting "with exit code
255"?
You are receiving this mail because:
- You are watching all bug changes.
