[I originally filed this downstream in Fedora's bug tracker here:
 https://bugzilla.redhat.com/show_bug.cgi?id=800113 ]

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
pygoocanvas-0.14.1-6.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/pygoocanvas-0.14.1-6.fc17/

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

Within the category "Reference leaks" the 2 issues reported appear to be
genuine  memory leaks in error-handling paths: the error-handling clauses need
a Py_DECREF(tuple)

Within the category "Segfaults within error-handling paths" the 3 issues
reported appear to be genuine crashers where an allocation fails and returns
NULL; however, given that GLib aborts the process when an allocation fails,
this may be already be a lost cause.

Within the category "Possible reference leaks" the first 2 of the 3 issues
reported appear to be false positives, which I've filed as
https://fedorahosted.org/gcc-python-plugin/ticket/36 ; the third issue is
inconsequential.

Within the category "Returning (PyObject*)NULL without setting an exception"
the 11 issues reported appear to be false positives.
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):
pygoocanvas-0.14.1-6.fc17
gcc-python-plugin post-0.9 git 11462291a66c8db693c8884cb84b795bb5988ffb running
the checker in an *f16* chroot