On Tue, Apr 5, 2011 at 4:32 PM, Paul Pluzhnikov <[email protected]> wrote:
> Safer? I don't see how. You are still calling pthread_setspecific from a > potentially unsafe context. I meant: it gives us some freedom to move pthread_setspecific() call around. Like you observe, there is no safe place to call it from within libunwind. I lean towards #3: . Switch to using __thread, figure out some (likely extremely non-portable) way to perform cleanup on thread termination. This could be as simple as documenting a function that users are required to call on thread idle/exit to cleanup. -Arun _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
