Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Bugs found in claws-mail-plugins-3.8.0-4.fc17 using gcc-with-cpychecker static analyzer|
|Product:||[Fedora] Fedora||Reporter:||Dave Malcolm <dmalcolm>|
|Component:||claws-mail-plugins||Assignee:||Andreas Bierfert <andreas.bierfert>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2015-02-17 09:07:24 EST||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Dave Malcolm 2012-02-16 10:55:03 EST
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 claws-mail-plugins-3.8.0-4.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-02-16/claws-mail-plugins-3.8.0-4.fc17/ I manually inspected the results there. There appear to at least 5 real bugs in the reports there: although the issue reported in the "Segfaults in normal paths" category appears to have been misfiled, and should be in the "Segfaults within error-handling paths" category, together, the 5 bugs listed there appear to be genuine crashers that could occur under low memory conditions, where the code isn't checking for a NULL return from Py_BuildValue. The reports in the other categories ("Possible reference leaks" and "Returning (PyObject*)NULL without setting an exception") look like they're probably false positives, rather than real bugs. There may of course be 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): claws-mail-plugins-3.8.0-4.fc17 gcc-python-plugin post-0.9 git 073d390de53ef52136bd90e5ac06f1ef833d047d running the checker in an *f16* chroot
Comment 1 Dave Malcolm 2012-02-16 11:05:11 EST
(In reply to comment #0) On further review, I think the issue reported in the "Segfaults in normal paths" category is a false positive, given that it can only happen if the "ComposeWindow" class is not found in the module dict (the checker can't know that this will succeed, and hence erroneously reports the possible failure). However, I still think that the 4 issues reported in "Segfaults within error-handling paths" are genuine bugs.
Comment 2 Fedora End Of Life 2013-04-03 09:42:19 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: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Comment 3 Michael Schwendt 2013-07-13 12:06:55 EDT
I've forwarded this aging ticket into the upstream tracker: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2970
Comment 4 Fedora End Of Life 2015-01-09 12:00:53 EST
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2015-02-17 09:07:24 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.