This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Alexander Riccio, christian.heimes, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2015-12-12.15:58:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1449935898.28.0.687506861653.issue25847@psf.upfronthosting.co.za>
In-reply-to
Content
Is analyze something that can be used from the command line only, or does it require the GUI?  Also, we aren't likely to make the code more complex in order to deal with shortcomings in analyze's algorithms (meaning in that case we couldn't turn it on automatically).  For valgrind, for example, we have an exceptions list, and similarly for covarity.  Does analyze support something similar?

I'm surprised it is catching things that coverity doesn't.
History
Date User Action Args
2015-12-12 15:58:18r.david.murraysetrecipients: + r.david.murray, paul.moore, christian.heimes, tim.golden, zach.ware, steve.dower, Alexander Riccio
2015-12-12 15:58:18r.david.murraysetmessageid: <1449935898.28.0.687506861653.issue25847@psf.upfronthosting.co.za>
2015-12-12 15:58:18r.david.murraylinkissue25847 messages
2015-12-12 15:58:18r.david.murraycreate