Description of problem:
I've been writing an experimental static analysis tool to detect bugs commonly occurring within C Python extension modules:
  https://fedorahosted.org/gcc-python-plugin/
  http://gcc-python-plugin.readthedocs.org/en/latest/cpychecker.html
  http://fedoraproject.org/wiki/Features/StaticAnalysisOfPythonRefcounts

I ran the latest version of the tool (in git master; post 0.9) on
pyOpenSSL-0.12-2.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):
http://fedorapeople.org/~dmalcolm/gcc-python-plugin/2012-03-05/pyOpenSSL-0.12-2.fc17/

I've manually reviewed the issues reported by the tool.

Within the category "Reference leaks" the 1 issue reported seems to be a genuine memory leak when OpenSSL/crypto/crypto.c:global_passphrase_callback receives an object that isn't of the bytes type.

Within the category "Reference count too low within an initialization routine" the 1 issue reported appears to be inconsequential.

Within the category "Segfaults within error-handling paths" the 1 issue reported appears to be a genuine crasher that could occur under low-memory conditions; it needs an:
   if (argv == NULL) {
       return NULL;
   }
or similar.

Within the category "Returning (PyObject*)NULL without setting an exception" the 12 issues reported appear to all be false positives: the checker doesn't know that exception_from_error_queue(crypto_Error) presumably sets the thread's exception state.

There may of course be other bugs in my checker tool.

Hope this is helpful; let me know if you need help reading the logs that the tool generates - I know that it could use some improvement.

Version-Release number of selected component (if applicable):
pyOpenSSL-0.12-2.fc17
gcc-python-plugin post-0.9 git 11462291a66c8db693c8884cb84b795bb5988ffb running the checker in an *f16* chroot