Wireshark-bugs: [Wireshark-bugs] [Bug 13049] Buildbot crash output: fuzz-2016-10-24-11612.pcap
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 15 Nov 2016 09:50:02 +0000

Comment # 21 on bug 13049 from 
(In reply to Gerald Combs from comment #16)
> (In reply to Pascal Quantin from comment #15)
> > (In reply to Pascal Quantin from comment #3)
> > > No problem running this capture on my machine. Given the size of the pcap
> > > (28.1 MB) I guess the buildbot ran out of memory without an infinite loop.
> > 
> > Gerald, is there a way to confirm this?
> 
> That appears to be the case. With the default (unlimited) virtual memory
> limit "valgrind --tool=memcheck tshark" takes a while but completes. With
> the virtual memory limit set to 750000 (which is what valgrind-wireshark.sh
> uses) it crashes with an allocation error.

So should we remove the ulimit when fuzzing with valgrind memchek, as we did
for ASAN?

You are receiving this mail because:
  • You are watching all bug changes.