On Fri, Oct 26, 2012 at 10:35 AM, Paul Pluzhnikov <[email protected]> wrote:
> The hint to call unw_backtrace early in thread creation is not very useful > to tcmalloc users, as they have little control over exactly when > calloc is called during thread creation, or when tcmalloc decides to > record a stack trace. > I went back and read the earlier messages on the topic: http://lists.gnu.org/archive/html/libunwind-devel/2011-04/msg00030.html Back then, you thought something like unwind_per_thread_once() could work. What has changed since then? IIRC - the calloc originates from within pthread_setspecific() and all we need to do is force a call to setspecific() from a safe (guaranteed outside of malloc) context. Are there other calls to calloc you've discovered since then? -Arun _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
