Re: [Valgrind-users] Uninitialized access findings on non-static file scope variables that's been initialized?

[John R. <jr...@bi...>]

On 08/13/2015 12:47 AM, Jeffrey Walton wrote:
> ...why would Valgrind
> complain a boolean value is not initialized, even though its
> initialized to false in the source code and backed via BSS?

The most common reason is because some uninitialized value
was assigned to (or copied into) the value in question.  Of course you probably
claim that this is impossible, but an unknown bug enables almost anything.
Be sure to run with --track-origins=yes.

As others have noted, if you cannot post a concrete example
that illustrates the problem then you are not worth our time anymore.