Subject: Re: bug#9990: valgrind warning in add_row_entry

From: Eli Zaretskii <[email-masked]>
Date: Tue, 08 Nov 2011 22:35:54 +0200

> From: Andreas Schwab <[email-masked]>
> Cc: Dan Nicolaescu <[email-masked]>,  [email-masked]
> Date: Tue, 08 Nov 2011 19:44:28 +0100
> 
> Eli Zaretskii <[email-masked]> writes:
> 
> > Does valgrind know that row_table_size is initially zero because it is
> > static?
> 
> valgrind does not know anything about variables, only about memory
> locations.  It operates at the machine language level.

Does that mean valgrind can potentially flag as uninitialized every
static variable that isn't explicitly initialized at run time?
Because AFAIK static variables are initialized by the linker (is that
right?).