Micahel I spent some time digging into the libunwind test failures; from the large amount of discussion about failing tests on the mailing list it appears that there are an expected set of failures which vary depending on architecture.
On x86_64 (5 failures); I was able to cherry pick two fixes (one an actual bug and the other a work-around in the test for calls to calloc ); 2 tests are expected to fail (unsupported features on this arch) and the last is just broken (I see attempts to resolve in trunk). I was not able to compile some of the tests on arm and there is alot of discussion about hanging and failing tests on the ML for this arch. Looking at i386 and powerpc now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017972 Title: [MIR] google-perftools, libunwind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-perftools/+bug/1017972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
