Displaying 3 results from an estimated 3 matches for "allocator_may_return_nul".
Did you mean:
allocator_may_return_null
2017 Sep 06
2
Temporary disable ASan's allocator check
...4 PM, Kostya Serebryany <kcc at google.com> wrote:
>
>
>
> On Wed, Sep 6, 2017 at 8:43 AM, Jonas Devlieghere via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Hi all,
>
> Is it possible to change the value of ASan's allocator_may_return_null at runtime or somehow disable this check temporarily? If I install an LLVM bad_alloc_error_handler, ASan's allocator wrapper detects this first and terminates the process instead of returning 0, preventing the custom handler from being called.
>
> Is this question related to "r3125...
2017 Sep 06
2
Temporary disable ASan's allocator check
Hi all,
Is it possible to change the value of ASan's allocator_may_return_null at runtime or somehow disable this check temporarily? If I install an LLVM bad_alloc_error_handler, ASan's allocator wrapper detects this first and terminates the process instead of returning 0, preventing the custom handler from being called.
Thanks,
Jonas
2014 Dec 08
2
[LLVMdev] [RFC] Parsing runtime flags in sanitizers (ASan/LSan/UBSan)
On Mon, Dec 8, 2014 at 2:00 AM, Alexander Potapenko <glider at google.com>
wrote:
> Hope you're assuming there's always a single copy of common_flags in
> the process.
> This isn't the case for e.g. ASan+UBSan on Mac, but that's a broken setup.
>
> What if we let the tools protect specific flags (by adding a bool to
> each flag) once they set their values