Re: Adding "pass-through" ASan allocator

Hi, On 12 January 2018 at 08:37, Francis Ricci wrote: > Hi all, > > I may be missing something conceptually with the way ASan works, but > is there any reason that ASan couldn't pass-through allocations to the > user's allocator? For example: > > 1) User calls malloc() >

Re: __asan_default_options not called

On Tue, 18 Dec 2018 at 12:14, wrote: > > We have added __asan_default_option() so that asan canpickup default options > from it. > > However, those options are not applied. To see if __asan_default_options is > called, I added a log but even log is not printed which means >

Re: Address sanitizer issue with dlsym

On Wed, 19 Dec 2018 at 10:48, Ankur Raj wrote: > > Its part of a large and complected code base ! malloc and free wrappers > exists for some book keeping reason > and i am afraid i cant change it either ! > I don't know if there is way to get around this A possible solution to this is to

Re: TSAN and ASAN cannot work on aarch64 server

Hi, ASan's signal handler is catch SIGSEGV. It looks like your program is trying to dereference a nullptr. Unfortunately ASan doesn't seem to be able to produce a stacktrace in this case. I'd recommend running with gdb or lldb attached and disabling ASan's signal handler (set

Re: does gRPC play nice with ASAN?

The output from the original poster is **not** a seg-fault. It's ASan catching the fact that a huge allocation is being requested and by default ASan halts when it detects this. You can disable this behavior by setting "ASAN_OPTIONS=allocator_may_return_null=1" in your environment. If you set this

Re: ASAN: Unable to find a memory range after restricting VM on IOS

Hi Rodrigo, It looks like you might be hitting an issue that we are currently tracking internally inside Apple. We have a hypothesis on the cause problem but we currently don't have a reproducer. Can you share a reproducer with us? Having a reproducer would allow us to confirm our hypothesis