#31 closed defect (fixed)
segfault in rsa.so
| Reported by: | zooko | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Version: | 0.5.17 | Keywords: | security |
| Cc: | Launchpad Bug: |
Description
test_serialize_and_deserialize_signing_key_and_test (pycryptopp.test.test_rsa.SignAndVerify?) ... process killed by signal 11
program finished with exit code -1
That was with the current trunk -- [20090916031341-92b7f-0c97a42c6acaff34bcec8eb1216c14c8cdece8c3]
Change History (4)
comment:1 Changed at 2009-10-25T19:18:10Z by zooko
comment:2 Changed at 2009-10-26T18:11:35Z by zooko
It looks like this is a bug in the Ubuntu version of g++:
comment:3 Changed at 2009-11-01T20:17:54Z by zooko
- Resolution set to fixed
- Status changed from new to closed
fixed in Ubuntu
comment:4 Changed at 2014-07-22T18:09:00Z by zooko
duplicate of #34
Note: See
TracTickets for help on using
tickets.
Hm. I set up a builder which uses the system-supplied libcrypto++ (on Karmic) and it passes:
http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-karmic-yukyuk-syslib
Although the builder on the same machine that is building the embedded copy of libcrypto++ segfaults:
http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-karmic-yukyuk
This suggests that there is a bug in the embedded copy, right? But it doesn't appear on any other builders. So possibly there is a bug interaction between the embedded copy of libcrypto++ and the version of g++ that is in Karmic Koala? I just added to the show-tool-versions step to emit what version of g++ is present on each platform.