Comment # 11
on bug 9246
from Evan Huus
(In reply to comment #10)
> I don't seem to be able to reproduce your valgrind results using "valgrind
> --leak-check=full --free-fill=00 --read-var-info=yes tshark -r
> fuzz-2013-10-07-4478.pcap 2>leaks.txt"
>
> Can I get a hint as to how to reproduce what you're seeing?
I reproduce using the script distributed in the wireshark source:
"./tools/valgrind-wireshark.sh FILE"
The script does a bunch of work setting environment variables, adding extra
parameters etc and automatically hides stdout, so if you're valgrinding from a
build tree it makes life much simpler.
For this bug I have to add -T which adds all the tshark parameters necessary
for building and displaying the complete dissection tree, so my final command
is:
./tools/valgrind-wireshark.sh -T fuzz-2013-10-07-4478.pcap
to see the complete details of leaked memory (basically adding
--leak-check=full to valgrind) add the -l flag as as well, but it should not be
necessary to see the "Invalid read" errors.
You are receiving this mail because:
- You are watching all bug changes.
