Launchpad has imported 2 comments from the remote bug at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52236.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-02-13T17:00:37+00:00 Zooko Wilcox-O'Hearn wrote: Using this version of gcc-4.7.0 prerelease which is shipped in Fedora Rawhide: 4.7.0 20120126 (Red Hat 4.7.0-0.10), the resulting code segfaults. Valgrind reports this: ==9709== Invalid read of size 1 ==9709== at 0xB4FEE70: crypto_hash_sha512 (sha512-hash.c:40) ==9709== by 0xB4F8F23: crypto_sign_publickey (ed25519.c:30) ==9709== by 0xB4F7EEB: ed25519_publickey (ed25519module.c:48) ==9709== by 0x4F0A153: PyEval_EvalFrameEx (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4F0B7C0: PyEval_EvalCodeEx (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E9C2BA: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E78A1D: PyObject_Call (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E86EEF: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E78A1D: PyObject_Call (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4ECBC41: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4ECB8DB: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E78A1D: PyObject_Call (in /usr/lib64/libpython2.7.so.1.0) ==9709== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==9709== { <insert_a_suppression_name_here> Memcheck:Addr1 fun:crypto_hash_sha512 fun:crypto_sign_publickey fun:ed25519_publickey fun:PyEval_EvalFrameEx fun:PyEval_EvalCodeEx obj:/usr/lib64/libpython2.7.so.1.0 fun:PyObject_Call obj:/usr/lib64/libpython2.7.so.1.0 fun:PyObject_Call obj:/usr/lib64/libpython2.7.so.1.0 obj:/usr/lib64/libpython2.7.so.1.0 fun:PyObject_Call } ==9709== ==9709== Process terminating with default action of signal 11 (SIGSEGV) ==9709== Access not within mapped region at address 0x0 ==9709== at 0xB4FEE70: crypto_hash_sha512 (sha512-hash.c:40) ==9709== by 0xB4F8F23: crypto_sign_publickey (ed25519.c:30) ==9709== by 0xB4F7EEB: ed25519_publickey (ed25519module.c:48) ==9709== by 0x4F0A153: PyEval_EvalFrameEx (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4F0B7C0: PyEval_EvalCodeEx (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E9C2BA: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E78A1D: PyObject_Call (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E86EEF: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E78A1D: PyObject_Call (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4ECBC41: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4ECB8DB: ??? (in /usr/lib64/libpython2.7.so.1.0) ==9709== by 0x4E78A1D: PyObject_Call (in /usr/lib64/libpython2.7.so.1.0) More detail, including access to a buildbot which can reliably reproduce the problem on Fedora Rawhide and demonstrate no such problem on several other platforms, is here: https://tahoe- lafs.org/trac/pycryptopp/ticket/80 Reply at: https://bugs.launchpad.net/gcc/+bug/931542/comments/0 ------------------------------------------------------------------------ On 2012-02-13T17:03:49+00:00 Zooko Wilcox-O'Hearn wrote: The host is linux x86_64. More information about the platform is queried automatically by the buildbot and archived here: https://tahoe-lafs.org /buildbot-pycryptopp/builders/Ruben%20Fedora%20syslib/builds/44/steps /show-tool-versions/logs/stdio platform: Linux-3.2.1-8.fc17.x86_64-x86_64-with-fedora-17-Rawhide machine: x86_64 linux_distribution: ('Fedora', '17', 'Rawhide') Reply at: https://bugs.launchpad.net/gcc/+bug/931542/comments/1 ** Changed in: gcc Status: Unknown => New ** Changed in: gcc Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931542 Title: using the gcc-4.7.0 prerelease as packaged by Fedora Rawhide, there is a segfault in the program that results from compiling sha512-hash.c To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/931542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
