** Description changed: Currently, in wily, some landing silos are blocked now, due to a segfault occurring when attempting to run certain test binaries, which depend on the gnutls stack. Most notably so far, I've hit this issue in projects which are using QtNetwork or libcurl for network access. The issue is a crash in libnettle6, with the following stack trace: Program received signal SIGSEGV, Segmentation fault. 0xb6c20b00 in nettle_yarrow256_update () - from /usr/lib/arm-linux-gnueabihf/libnettle.so.6 + from /usr/lib/arm-linux-gnueabihf/libnettle.so.6 (gdb) bt #0 0xb6c20b00 in nettle_yarrow256_update () - from /usr/lib/arm-linux-gnueabihf/libnettle.so.6 + from /usr/lib/arm-linux-gnueabihf/libnettle.so.6 #1 0xb6bd6406 in ?? () from /usr/lib/arm-linux-gnueabihf/libgnutls-deb0.so.28 Backtrace stopped: previous frame identical to this frame (corrupt stack?) There seems to also be no dbgsym package available yet on ddebs.ubuntu.com for this package, so I've not been able to get a more complete trace. + + This is happening with nettle 3.1.1-3 in wily-proposed.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463875 Title: Crash in libnettle6 on armhf and powerpc archs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1463875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
