On Fri, Nov 22, 2013 at 11:13:26PM +0400, Konstantin Serebryany wrote:
> +eugenis, dvyukov
> libbacktrace doesn't call malloc -- good.
> Most other functions it does call (memset,strlen, etc) will be
> rerouted to sanitizer interceptors.
> This is just generally scary and I think we've been hit by this in
> reality with early llvm-symbolizer.
> More likely in tsan and msan than in asan.
> Evgeniy, Dmitry, do you remember any details?
While it can look scary, most of the functions are actually async signal
safe functions so even if libbacktrace doesn't call them, user code in async
signal handlers might call them any time.
>From brief skimming you are only intercepting the async-signal-safe
functions from this list.
> > U bsearch
> > U memcpy
> > U memset
> > U qsort
> > U snprintf
> > U strcmp
> > U strlen
> > U strnlen
> > U close
> > U __errno_location
> > U fcntl
> > U open
> > U dl_iterate_phdr
> > U getpagesize
> > U mmap
> > U munmap
Jakub
