Project

General

Profile

Actions

Feature #2772

open

112: Check that variables are initialized before usage

Added by Evgeny Novikov over 12 years ago. Updated over 12 years ago.

Status:
Open
Priority:
Normal
Start date:
04/19/2012
Due date:
% Done:

0%

Estimated time:
Published in build:

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.

Actions #1

Updated by Evgeny Novikov over 12 years ago

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.

Actions #2

Updated by Alexey Khoroshilov over 12 years ago

  • Subject changed from Check that variables are initialized before usage to 112: Check that variables are initialized before usage
Actions #3

Updated by Evgeny Novikov over 12 years ago

  • Priority changed from High to Normal

Reduce priority until we'll decide that it's high actually.

Actions

Also available in: Atom PDF