Good day everyone. I am thinking of performing a static code analysis of the source code for possible security and code problems before every release. I think this will help to enhance the software quality.

I wish to see static source code analysis to be an integral part of the Bitcoin development process. I am not sure if the present code was checked for possible buffer overflow attacks or null pointer dereferencing problems or other critical code problems.

Any suggestions in these lines are welcome.

1) Which static code analsysis should we prefer or any good new static code analysis tools you are aware of which is FREE?2) How can we ensure every developer is forced to make this a mandatory step in the development process?

It would probably be better to send this kind of information privately to the developers. There is no need to post it publicly unless they ignore you. There is a list of developers and their emails on www.bitcoin.org.

As we slide down the banister of life, this is just another splinter in our ass.

It would probably be better to send this kind of information privately to the developers. There is no need to post it publicly unless they ignore you. There is a list of developers and their emails on www.bitcoin.org.

Thanks for your suggestion. I just tried to post these issues to generate a healthy discussion of the use of some robust static analysis tool for the bitcoin project.

It would probably be better to send this kind of information privately to the developers. There is no need to post it publicly unless they ignore you. There is a list of developers and their emails on www.bitcoin.org.

Thanks for your suggestion. I just tried to post these issues to generate a healthy discussion of the use of some robust static analysis tool for the bitcoin project.

I have raised these issues in the github bitcon.

Just the some pointers from the client's GUI classes that aren't deallocated at clean up. Nothing serious, just messy coding.

It would probably be better to send this kind of information privately to the developers. There is no need to post it publicly unless they ignore you. There is a list of developers and their emails on www.bitcoin.org.

Thanks for your suggestion. I just tried to post these issues to generate a healthy discussion of the use of some robust static analysis tool for the bitcoin project.

I have raised these issues in the github bitcon.

Just the some pointers from the client's GUI classes that aren't deallocated at clean up. Nothing serious, just messy coding.

Thanks for your analysis. These errors can be safely classified as minors bugs in the code.