Bug 800158 - Bugs found in python-jinja-1.2-7.fc17 using gcc-with-cpychecker static analyzer
Bugs found in python-jinja-1.2-7.fc17 using gcc-with-cpychecker static analyzer
Product: Fedora
Classification: Fedora
Component: python-jinja (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Thomas Moschny
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
Blocks: cpychecker
  Show dependency treegraph
Reported: 2012-03-05 16:05 EST by Dave Malcolm
Modified: 2013-04-10 13:52 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Malcolm 2012-03-05 16:05:21 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-jinja-1.2-7.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):

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

Within the category "Segfaults within error-handling paths" the 3 issues reported appear to be genuine crashers under low-memory conditions, where the code assumes that PyMem_Malloc() succeeds.

Within the category "Returning (PyObject*)NULL without setting an exception" the 1 issue reported appears to be a genuine bug: PyMem_Malloc() doesn't set an exception when it fails.

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):
gcc-python-plugin post-0.9 git 11462291a66c8db693c8884cb84b795bb5988ffb running the checker in an *f16* chroot
Comment 1 Thomas Moschny 2012-03-16 13:46:46 EDT
Not sure what to do with this bug. jinja is not actively developed anymore. In Fedora, only olpc-library depends on it.

So I guess upstream is not interested in fixing these bugs, and I don't have enough time to do so. If you provide patches, I'll happily integrate them though. The speedup module is now part of python-markupsafe, so maybe one can backport something from there.
Comment 2 Fedora End Of Life 2013-04-03 15:46:27 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:

Note You need to log in before you can comment on or make changes to this bug.