On 07 May 2015, at 10:40, Mike McTernan (wavemobile) mike.mcternan@wavemobile.com wrote:
Hi!
It wouldn't have helped here, but since ASAN is discussed in the context of memory errors, I'd like to check that it's been considered that ASAN's ability to detect and report memory errors may be being impaired by the use of talloc - particularly use after free bugs.
On double talloc_free I do get aborts from the libc memory management. We don’t use the pool feature (yet) so all calls to talloc_free/talloc_alloc will go directly to malloc/free and should be handled by ASAN.
holger