From 064174efa3604404fd1b8a5c34cf69ed93ab12dc Mon Sep 17 00:00:00 2001
From: Michael Vetter <jubalh@iodoru.org>
Date: Wed, 24 Mar 2021 17:20:54 +0100
Subject: [PATCH] debug build: build without -fsanitize=address

Sorry :-)
Seems then we can't use valgrind since that does its own ASAN things.

So maybe developers needs to set some flags by themselves to find these
memory issues.

https://fuzzing-project.org/tutorial-cflags.html might be of help.

Regards: https://github.com/profanity-im/profanity/issues/1512
---
 configure-debug | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure-debug b/configure-debug
index e0fad154..63679c98 100755
--- a/configure-debug
+++ b/configure-debug
@@ -1,4 +1,4 @@
 #!/bin/sh
 
 #./configure PYTHON_VERSION=3 CFLAGS='-g3 -O0' CXXFLAGS='-g3 -O0' $@
-./configure CFLAGS='-g3 -O0 -fsanitize=address' CXXFLAGS='-g3 -O0' $@
+./configure CFLAGS='-g3 -O0' CXXFLAGS='-g3 -O0' $@