Displaying 3 results from an estimated 3 matches for "c_exampl".
Did you mean:
c_example
2016 Feb 09
3
Buildling with/without AddressSanitizer causes divergent execution behaviour
...basics of
what I found.
Build Z3 as follows
```
git clone https://github.com/Z3Prover/z3.git
cd z3
# Now apply the attached patch.
# Basically this makes it so that in ``examples/c/test_capi.c``
# the main() function only calls two functions.
# Note if you build without the patch when running ``c_example``
program AddressSanitizer
# reports a heap-use-after-free. I'm not sure if this a false positive
or not. Valgrind doesn't
# seem to think there's a problem.
# Build with ASan, Assertion will be hit when running the example
CXX=clang++ CC=clang CXXFLAGS="-fno-omit-frame-pointer
-...
2016 Feb 11
3
Buildling with/without AddressSanitizer causes divergent execution behaviour
...antine_size_mb=N, default=256)
> Valgrind may have smaller default quarantine and thus misses this bug.
I was lazy and just told valgrind to execute the program (built by gcc
without ASan) with the largest quarantine it supported.
```
LD_LIBRARY_PATH=`pwd` valgrind --freelist-vol=10000000000 ./c_example
```
It didn't report any problems. This fills me with some confidence that
when the application is compiled without ASan that it probably doesn't
have a heap-use-after-free.
> Does the application have threads? (If yes, did you run with TSan?)
Not yet but I've stumbled across an...
2016 Feb 12
3
[cfe-dev] Buildling with/without AddressSanitizer causes divergent execution behaviour
On 11 February 2016 at 17:08, Reid Kleckner <rnk at google.com> wrote:
> On Thu, Feb 11, 2016 at 5:53 AM, Dan Liew via cfe-dev
> <cfe-dev at lists.llvm.org> wrote:
>>
>> > Can you somehow verify that this heap-use-after-free is happening?
>> > E.g. print all the pointer values coming from memory::allocate, coming
>> > into
>> >