On 10/26/12 10:35 AM, Paul Pluzhnikov 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.
True. The workaround is practical only for folks who have the ability to force something right after thread creation, but before any calls to malloc related routines.
I would prefer the test to fail while unw_backtrace() remains calloc-unsafe. If the flood of "Ltest-nocalloc is failing" messages from end-users is too distracting, perhaps there should be a "currently known to fail" set of tests that only maintainers would know how to run?
That was the motivation. I'll lookup the documentation on XFAIL_TESTS this weekend.
-Arun _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
