Hi, I'm trying to figure out a way to let a custom allocator be able to report leaked object through lsan. Presumably we could just do everything in the allocator since it's customized already. But we don't really want to repeat the effort that has been done by lsan like tracking the live object, collect the allocation stacktraces, etc.
We are using ASAN_POISON_MEMORY_REGION so that at least we can detect use after free with the custom allocator, but unfortunately it doesn't cover the lsan portion. __lsan_register_root_region/__lsan_unregister_root_region seem to be something close, but somehow lsan doesn't report memory leak even if there is a missing __lsan_unregister_root_region in our test. Any other hint? Thanks! - Ming -- 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.
