Feature #2772
open
112: Check that variables are initialized before usage
Added by Evgeny Novikov about 12 years ago.
Updated about 12 years ago.
Description
This is very hard rule to be formulated for high-weight static analysis tools because of it's too generic. But we can try to do this in some cases. Say, commit c6fedb5 of linux-stable branch fixed an error related with 'extra_len' variable may be used uninitialized. This issue belongs to generic:uninit in our classifier. Model 112_1a will try to find it.
3b9422f commit of our master branch added support of 112_1a model, that finds the error before the commit c6fedb5 and finds safe after the commit. Please note, that I have thought that this model requires BLAST_ALIASES environment variable to be set up, but it turns out that this isn't the case. I.e. BLAST works with simple pointer dereferences (even when variable is passed to another function) by default.
- Subject changed from Check that variables are initialized before usage to 112: Check that variables are initialized before usage
- Priority changed from High to Normal
Reduce priority until we'll decide that it's high actually.
Also available in: Atom
PDF