[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#9990: valgrind warning in add_row_entry
From: |
Eli Zaretskii |
Subject: |
bug#9990: valgrind warning in add_row_entry |
Date: |
Tue, 08 Nov 2011 22:35:54 +0200 |
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Dan Nicolaescu <dann@gnu.org>, 9990@debbugs.gnu.org
> Date: Tue, 08 Nov 2011 19:44:28 +0100
>
> Eli Zaretskii <eliz@gnu.org> 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?).
- bug#9990: valgrind warning in add_row_entry, Dan Nicolaescu, 2011/11/08
- bug#9990: valgrind warning in add_row_entry, Eli Zaretskii, 2011/11/08
- bug#9990: valgrind warning in add_row_entry, Andreas Schwab, 2011/11/08
- bug#9990: valgrind warning in add_row_entry,
Eli Zaretskii <=
- bug#9990: valgrind warning in add_row_entry, Dan Nicolaescu, 2011/11/11
- bug#9990: valgrind warning in add_row_entry, Eli Zaretskii, 2011/11/11
- bug#9990: valgrind warning in add_row_entry, Eli Zaretskii, 2011/11/11
- bug#9990: valgrind warning in add_row_entry, Dan Nicolaescu, 2011/11/11
- bug#9990: valgrind warning in add_row_entry, Eli Zaretskii, 2011/11/12
- bug#9990: valgrind warning in add_row_entry, Dan Nicolaescu, 2011/11/15
- bug#9990: valgrind warning in add_row_entry, Eli Zaretskii, 2011/11/15
- bug#9990: valgrind warning in add_row_entry, Eli Zaretskii, 2011/11/18
- bug#9990: valgrind warning in add_row_entry, Dan Nicolaescu, 2011/11/18
- bug#9990: valgrind warning in add_row_entry, Eli Zaretskii, 2011/11/18