about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorMichael Vetter <jubalh@iodoru.org>2021-03-24 17:20:54 +0100
committerMichael Vetter <jubalh@iodoru.org>2021-03-24 17:20:54 +0100
commit064174efa3604404fd1b8a5c34cf69ed93ab12dc (patch)
tree1703b920ebb185f42e3c9695eb034904ba799ee6
parent5f7840bc3fc316a2b14a043cf65d5f7db32e0717 (diff)
downloadprofani-tty-064174efa3604404fd1b8a5c34cf69ed93ab12dc.tar.gz
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
-rwxr-xr-xconfigure-debug2
1 files changed, 1 insertions, 1 deletions
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' $@