On Wed, Aug 10, 2011 at 7:47 PM, Theodore Ts'o <[email protected]> wrote:
> =========================================== > 5 of 29 tests failed > Please report to [email protected] > =========================================== >[..] > Does this ring a bell? Is there anything I should try? This is with > the latest git checkout of libunwind. > These are known failures (functionality not implemented on x86_64 yet). But it shouldn't impact the common use cases (local unwinding). The larger issue libunwind faces is due to APIs that call malloc or ones which take locks: * dl_iterate_phdr * pthread_setspecific The latter is easy to work around. The former requires a lock free, malloc free implementation of dl_iterate_phdr. -Arun _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
