Displaying 4 results from an estimated 4 matches for "asan_allocator".
Did you mean:
msan_allocator
2015 Aug 11
3
libfuzzer questions
First off, thanks -- this is a pretty great library and it feels like I'm
learning a lot. I'm getting some more experience with libfuzzer and
finding that I have a couple of questions:
- How does libfuzzer decide to write a new test file? What distinguishes
this one from all the other cases for which new test inputs were not
written? Must be something about the path taken through the
2015 Aug 11
3
libfuzzer questions
...true, alloc_type=__asan::FROM_MALLOC, stack=0x7fffd956a360, alignment=8, size=<optimized out>, this=0x192db80 <__asan::instance>)
#9 __asan::asan_malloc (size=size at entry=4096, stack=stack at entry=0x7fffd956a360) at /home/brian/tmp/testing/llvm_src/llvm/projects/compiler-rt/lib/asan/asan_allocator.cc:718
#10 0x00000000004da852 in __interceptor_malloc (size=4096) at /home/brian/tmp/testing/llvm_src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:41
#11 0x00007f76e14dfc65 in operator new(unsigned long) () from /home/brian/tmp/testing/testing_install//lib/libc++.so.1
#12 0x00007f76e14df...
2015 Sep 25
2
Dynamic VMA in Sanitizers for AArch64
Jakub makes a good point, are you sure that there is no single shadow
offset value that works for all VMA variants? What exactly breaks when
1<<36 is used on 42-bit VMA?
On Fri, Sep 25, 2015 at 3:28 AM, Yury Gribov via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> On 09/25/2015 01:27 PM, Yury Gribov wrote:
>>
>> On 09/25/2015 11:53 AM, Jakub Jelinek via llvm-dev
2019 Jan 24
2
[Release-testers] [8.0.0 Release] rc1 has been tagged
On Thu, 2019-01-24 at 19:58 +0100, Dimitry Andric via Release-testers
wrote:
> On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:
> >
> > 8.0.0-rc1 was just tagged (from the branch at r351980).
> >
> > It took a little longer than planned, but it's looking good.
> >
> > Please run the test