Prev Up Next

Bauhaus reports 91 different occurrences of uses of potentially uninitialized variables for concepts. Many of these findings turn out to be OK at a closer inspection. They were reported because the analysis conservatively assumes that every control path can actually be taken (recognizing infeasible paths is undecidable in general). But would you have preferred to analyze all uses of variables instead? Well, there are 3329 uses of variables in concepts...

Here is an example of a potentially uninitialized variable:

Function ArrowJoinConcepts reads setsize, which is potentially uninitialized. Variable setsize is local and the only occurence up to this point is in the call to ArrowCreateArray two lines earlier where it is passed as a reference parameter.

Let us analyze the body of ArrowCreateArray who apparently does not define the value of setsize under all circumstances.