Re: Memory leak debugging - current master passes all tests!

[Jeff Morriss <jeff.morriss.ws () gmail com>]

On Mon, Jan 28, 2019 at 4:03 PM Peter Wu <peter () lekensteyn nl> wrote:

> If you have not already, consider enabling ASAN by default in your
> development builds (cmake -DENABLE_ASAN=1). It works on Linux and macOS,
> but not with MSVC. ASAN detect memory safety issues (use-after-free,
> double-free, buffer overflows, etc.) and is faster than valgrind.
>
> If you do need valgrind, note that ASAN is not compatible with it. In
> this case, simply create another build directory without ASAN.
>
> If you are just interested in memory safety checks, but not memory leak
> debugging, simply disable the latter with:
>
>     export ASAN_OPTIONS=detect_leaks=0
>
> These ASAN options are documented at
> https://github.com/google/sanitizers/wiki/AddressSanitizerFlags

Nice info.  I had wondered at some points how to run ASAN but not enough to
do the (probably minimal) research.  Could I suggest putting the info in a
Wiki page?  (When I look for info I look in the READMEs and the wiki; I
rarely search the email archives unless I remember what I was looking for
being there.)

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