Problems have been found with the following capture file:https://www.wireshark.org/download/automated/captures/fuzz-2016-08-23-23680.pcapstderr:Input file: /home/wireshark/menagerie/menagerie/10484-frame31.capBuild host information:Linux wsbb04 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/LinuxDistributor ID: UbuntuDescription: Ubuntu 16.04.1 LTSRelease: 16.04Codename: xenialBuildbot information:BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wiresharkBUILDBOT_WORKERNAME=fuzz-testBUILDBOT_BUILDNUMBER=51BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/BUILDBOT_BUILDERNAME=Fuzz TestBUILDBOT_GOT_REVISION=2697dbb2895b6205e03275a53b0cc7f23b7b95b0Return value: 0Dissector bug: 0Valgrind error count: 1Git commitcommit 2697dbb2895b6205e03275a53b0cc7f23b7b95b0Author: Guy Harris <guy@alum.mit.edu>Date: Mon Aug 22 20:36:24 2016 -0700 See if *this* convinces the compiler that valuelen and value will be set. Change-Id: I2a7715ac3255502f244a0d0a7e588b3a44c34f11 Reviewed-on: https://code.wireshark.org/review/17258 Reviewed-by: Guy Harris <guy@alum.mit.edu> (cherry picked from commit bee0cd776219fc3cd6ac6a932a1d25b944c299a0) Reviewed-on: https://code.wireshark.org/review/17259==12924== Memcheck, a memory error detector==12924== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.==12924== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info==12924== Command: /home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr /fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-23-23680.pcap==12924====12924====12924== HEAP SUMMARY:==12924== in use at exit: 858,894 bytes in 26,971 blocks==12924== total heap usage: 296,392 allocs, 269,421 frees, 36,496,437 bytes allocated==12924====12924== LEAK SUMMARY:==12924== definitely lost: 3,388 bytes in 151 blocks==12924== indirectly lost: 405,530 bytes in 17,121 blocks==12924== possibly lost: 0 bytes in 0 blocks==12924== still reachable: 449,976 bytes in 9,699 blocks==12924== suppressed: 0 bytes in 0 blocks==12924== Rerun with --leak-check=full to see details of leaked memory==12924====12924== For counts of detected and suppressed errors, rerun with: -v==12924== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)[ no debug trace ]