Displaying 2 results from an estimated 2 matches for "z3_upstream".
2016 Feb 11
3
Buildling with/without AddressSanitizer causes divergent execution behaviour
...FLAGS="-fsanitize=memory" python scripts/mk_make.py --build
build_msan_clang --noomp --debug
cd build_msan_clang
make
make c_example
LD_LIBRARY_PATH=`pwd` ./c_example
==26936==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x7fa7d906f3b0 in Z3_open_log
/home/dsl11/dev/klee/z3/z3_upstream/build_msan_clang/../src/api/api_log.cpp:33:13
#1 0x55c0c03107f5 in main
/home/dsl11/dev/klee/z3/z3_upstream/build_msan_clang/../examples/c/test_capi.c:2794:5
#2 0x7fa7d78f960f in __libc_start_main (/usr/lib/libc.so.6+0x2060f)
#3 0x55c0c024d838 in _start
(/home/dsl11/dev/klee/z3/z3_upstr...
2016 Feb 09
3
Buildling with/without AddressSanitizer causes divergent execution behaviour
Hi,
# TL;DR
I've been building an application with and without the address
sanitizer (with gcc 5.3 and clang 3.7.1) and I've observed that the
application's behaviour changes (assertion hit/ not hit). I'm
wondering if this could be a bug in address sanitizer or if the
application I'm running is just buggy (e.g. doing bad things like
relying on memory layout, etc.). I'm