Displaying 2 results from an estimated 2 matches for "g_z3_log".
2016 Feb 11
3
Buildling with/without AddressSanitizer causes divergent execution behaviour
...```
Side note using ``MSAN_OPTIONS="halt_on_error=0`` doesn't seem to do
anything, the application always exits when it hits the reported bug.
I'd like a way to catch this in gdb but I'm not sure how to do it.
I took a look. MSan is complaining about this code
```
std::ostream * g_z3_log = 0;
...
Z3_bool Z3_API Z3_open_log(Z3_string filename) {
if (g_z3_log != 0)
Z3_close_log();
g_z3_log = alloc(std::ofstream, filename);
g_z3_log_enabled = true;
if (g_z3_log->bad() || g_z3_log->fail()) {
dealloc(g_z3_log);...
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