From: Richard Levitte <levitte@openssl.org>
Date: Tue, 2 Jul 2019 14:23:27 +0000 (+0200)
Subject: Use leak sanitizer instead of internal mdebug to check for memory leaks
X-Git-Tag: openssl-3.0.0-alpha1~843
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=22c22369bc09988eb8c6fdf4f543581a78fd3eb1;p=oweals%2Fopenssl.git

Use leak sanitizer instead of internal mdebug to check for memory leaks

The leak sanitizer gives better reports (complete stack traces) and
works as a wrapper around the application instead of relying on
cooperative enabling and disabling calls (which are too easy to get
unbalanced).

Related to #8322

Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/9294)
---

diff --git a/.travis.yml b/.travis.yml
index 5e65d37795..6d0fa801e8 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -27,7 +27,7 @@ compiler:
 
 env:
     - CONFIG_OPTS="" DESTDIR="_install"
-    - CONFIG_OPTS="no-asm -Werror --debug no-afalgeng no-shared enable-crypto-mdebug enable-rc5 enable-md2"
+    - CONFIG_OPTS="no-asm -Werror --debug no-afalgeng no-shared enable-rc5 enable-md2 -fsanitize=address" LSAN_OPTIONS="report_objects=1"
     - CONFIG_OPTS="no-asm no-makedepend enable-buildtest-c++ --strict-warnings -D_DEFAULT_SOURCE" BUILDONLY="yes" CHECKDOCS="yes" GENERATE="yes" CPPFLAGS="-ansi"
 
 matrix: