On Sat, Mar 22, 2014 at 4:41 PM, Hadriel Kaplan
<[email protected]> wrote:
> On Mar 21, 2014, at 5:31 PM, Guy Harris <[email protected]> wrote:
>> On Mar 21, 2014, at 2:18 PM, Hadriel Kaplan <[email protected]> wrote:
>>> How long does the clang code analysis buldbot
>> You mean the "beat the living hell out of Wireshark to look for bugs in many different ways" buildbot? :-)
> What does it actually *do*? It looks like some of the crash bugs it submits are GUI-specific and only occur way down the packet list, so presumably it actually loads the fuzzed files in wireshark and scrolls down the list. Does it also try some of the graphs/analyzers?
> I ask because I can't repo a crash with bug 9887 by just viewing it, but if I select Telephony->Voip Calls... boom goes the dynamite.
Only fuzzing the dissector code (with tshark)
there is no fuzzing (or automatic test ) for GUI (Wireshark)
> Sent via: Wireshark-dev mailing list <[email protected]>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:[email protected]?subject=unsubscribe