Comment # 6
on bug 8030
from Evan Huus
(In reply to comment #5)
> The only way I've been able to reproduce this is with the
> 'test-fuzzed-capture' script running under valgrind (with trace-children).
> Basically running the following:
>
> valgrind --trace-children=yes ./tools/test-fuzzed-cap.sh
> fuzz-2012-11-30-1917.pcap
>
> gives some unusual errors and unusual memory statistics.
This is probably misleading - it looks like just a side-effect of using glib
under valgrind without the G_SLICE=always-malloc environment variable that the
valgrind script sets.
So it looks like I really can't reproduce this one, but it keeps popping up in
the fuzz-tester... not sure what's going on here.
You are receiving this mail because:
- You are watching all bug changes.
