This is the gdb traceback seen while running the openstack provider tests: http://pastebin.ubuntu.com/9073749/
Funnily enough I saw a traceback very much like this just yesterday. What I know at this point: It's failing while parsing a https certificate. The failure occurs during allocation: go captures profiling data every $Nth allocation, and part of this profiling data is a traceback. Capturing this traceback hits a SIGBUS. I don't know why it always fails during https stuff -- maybe that code corrupts the stack? Or maybe that code just does more allocations and so is more likely to hit the profiling code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393825 Title: Juju testsuite fails in random ways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
