Displaying 3 results from an estimated 3 matches for "asan_poisoning".
2017 Jul 31
0
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
...up with all of these ASan failures? Is there a bug for it?
I spent a limited amount of debugging on it, but the common problem is that on i386 (aka 32-bit x86) all programs compiled with -fsanitize=address now die with:
==11122==AddressSanitizer CHECK failed: /usr/src/contrib/compiler-rt/lib/asan/asan_poisoning.cc:36 "((AddrIsAlignedByGranularity(addr))) != (0)" (0x0, 0x0)
#0 0x806f163 in __asan::AsanCheckFailed(char const*, int, char const, unsigned long long, unsigned long long) (/share/dim/src/misc/hw+0x806f163)
#1 0x805dce3 in __sanitizer::CheckFailed(char const*, int, char const, un...
2017 Jul 31
3
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric <dimitry at andric.com> wrote:
> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>>
>> 5.0.0-rc1 has just been tagged.
>>
>> Please build, test and upload binaries to the sftp. Let me know if
>> there are any issues.
>
> Built and tested rc1. Test failures on
2015 Sep 08
2
Some feedback on Libfuzzer
On Sat, Sep 5, 2015 at 11:50 AM, Greg Stark <stark at mit.edu> wrote:
> On Sat, Sep 5, 2015 at 6:38 PM, Kostya Serebryany <kcc at google.com> wrote:
> >
> > This is more like a limitation of asan, not libFuzzer.
> > By design, asan does not recover from the first crash.
> > This feature has been criticized quite a lot, but I am still convinced
> this
>