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() 2) ASan intercepts malloc(), does checks/adds metadata, etc 3) Instead of using the sanitizer allocator, ASan calls back into the user's malloc(). Barring technical challenges here with the way interception works, is there any reason this couldn't work from an allocation perspective? Would it just be very slow? Or does the sanitizer allocator actually do a lot of extra work besides just allocating memory? If the sanitizer allocator does extra work, perhaps the passthrough allocation could happen at that level instead, but still could be a possibility? It would be useful to be able to enable ASan on a codebase that uses a custom allocator without having to disable test coverage of that allocator by switching to ASan's allocator. Francis -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
