Public bug reported: g++-4.4 4.4.1-3ubuntu3 was used to build libcrypto++8. The current g++-4.4 in Karmic is g++-4.4 4.4.1-4ubuntu8. When 4.4.1-4ubuntu8 is used to build libcrypto++8 then the libcrypto++8 self-tests hang during the SHA validation. It appears that there has been a regression between g++ 4.4.1-3ubuntu3 and -4ubuntu8 such that the new one generates bad code.
In addition to the libcrypto++8 self-tests hanging during SHA validation, if you then build python-pycryptopp using the libcrypto++8 lib that was built by g++ 4.4.1-4ubuntu8, then the python-pycryptopp library gets segfaults when it runs its self-tests. Here is the pycryptopp upstream buildbot showing segfaults on karmic, along with a valgrind report: http://allmydata.org/buildbot-pycryptopp/waterfall http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-karmic-yukyuk/builds/11/steps/test/logs/valgrind ** Affects: gcc-4.4 (Ubuntu) Importance: Undecided Status: New ** Tags: regression-potential -- generates-bad-code regression https://bugs.launchpad.net/bugs/461303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
