Re: Clang build with ASAN

[Evan Huus <eapache () gmail com>]

On Tue, Aug 13, 2013 at 10:07 AM, Alexis La Goutte <
alexis.lagoutte () gmail com> wrote:

> On Tue, Aug 13, 2013 at 3:44 PM, Evan Huus <eapache () gmail com> wrote:
>
> > On Tue, Aug 13, 2013 at 6:29 AM, Bálint Réczey <balint () balintreczey hu>wrote:
> >
> > > Hi,
> > >
> > > 2013/8/12 Alexis La Goutte <alexis.lagoutte () gmail com>:
> > > > Hi,
> > > >
> > > > it is now possible to build wireshark with clang (CC=clang ./configure
> > > &&
> > > > make) (i fix last issue last week end).
> > > Great news!
> > >
> > > > I will try the ASAN feature (
> > > > http://clang.llvm.org/docs/AddressSanitizer.html )
> > > ASAN is also ported to GCC 4.8.
> > > I'm not sure which compiler is more reliable regarding ASAN checks,
> > > though.
> > >
> > > ...
> > > > Also may be now add a clang build to buildbot? (no only scan-build)
> > > I also wanted to raise the question of adding '-fsanitize=address'  to
> > > the C flags.
> > > I think fuzzing with ASAN would worth the extra CPU time on buildbots
> > > and I'm even considering
> > > turning ASAN on in the Debian packages by default.
> >
> > ASAN is basically a borrowed subset of valgrind, so fuzzing with ASAN is
> > not necessary if we can ever get fuzzing with valgrind to work...
> >
> > ASAN is only 2x slower (valgrind is 20x slower...) and some bugs is only
> detect by ASAN...

I knew it would be faster, but I didn't know it also detected stack errors
(and not just heap errors). However, it does not detect uninitialized reads
(which Valgrind does) so for full coverage we need to do both.


> ___________________________________________________________________________
> > Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> > Archives:    http://www.wireshark.org/lists/wireshark-dev
> > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> >              mailto:wireshark-dev-request () wireshark org
> > ?subject=unsubscribe
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe