Red Hat Bugzilla – Bug 790584
Segfaults in error-handling within pycrypto
Last modified: 2012-02-28 05:56:57 EST
Description of problem:
I've been writing an experimental static analysis tool to detect bugs commonly occurring within C Python extension modules:
I ran the latest version of the tool (in git master; post 0.9) on python-crypto-2.5-1.fc17.src.rpm, and it reports various errors.
You can see a list of errors here, triaged into categories (from most significant to least significant):
Note that the top-most bug there is a false positive (reported for "Segfaults in normal paths" - "Crypto.Random" always has a "new" member, though the checker can't know that)
I believe that the five errors reported within "Segfaults within error-handling paths" are genuine crashers, which could be seen under low memory conditions.
(There may of course be other bugs in my checker tool)
Version-Release number of selected component (if applicable):
[If this bug report is mystifying to you, let me know - I'm trying to iron out the wrinkles in the analysis tool]
I've reported this upstream:
I've included upstream's fixes for these issues in python-crypto-2.5-2 (built in Rawhide and building for F-17). Can you try re-running your checker on the new code?
python-crypto-2.5-2.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-crypto-2.5-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
python-crypto-2.5-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.