I managed to get clang / llvm 3.7 installed on the Code Analysis builder.
It's not yet compiling cleanly due to unused-arguments,
no-parentheses-equality, shorten-64-to-32, self-assign, and other errors
but it should hopefully be building soon. This also means that we should be
able to add ASAN che
Right, understood.
And if I'd actually carefully read the bug comments fuzzbot submits, I would
have noticed the './tshark -nVxr' at the bottom of them. :)
-hadriel
On Mar 22, 2014, at 1:54 PM, Guy Harris wrote:
>
> On Mar 22, 2014, at 8:41 AM, Hadriel Kaplan wrote:
>
>>
>> On Mar 21, 20
On Mar 22, 2014, at 8:41 AM, Hadriel Kaplan wrote:
>
> On Mar 21, 2014, at 5:31 PM, Guy Harris wrote:
>
>> On Mar 21, 2014, at 2:18 PM, Hadriel Kaplan
>> wrote:
>>
>>> How long does the clang code analysis buldbot
>>
>> You mean the "beat the living hell out of Wireshark to look for bugs
On Sat, Mar 22, 2014 at 4:41 PM, Hadriel Kaplan
wrote:
>
> On Mar 21, 2014, at 5:31 PM, Guy Harris wrote:
>
>> On Mar 21, 2014, at 2:18 PM, Hadriel Kaplan
>> wrote:
>>
>>> How long does the clang code analysis buldbot
>>
>> You mean the "beat the living hell out of Wireshark to look for bugs in
On Mar 21, 2014, at 5:31 PM, Guy Harris wrote:
> On Mar 21, 2014, at 2:18 PM, Hadriel Kaplan 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*?
On Mar 21, 2014, at 2:18 PM, Hadriel Kaplan 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? :-)
> run usually take?
If successful, a lng time. If we look at, for example, build
How long does the clang code analysis buldbot run usually take?
I ask because it appears to have been running for a lng time.
-hadriel
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lis
