Hi,
I'm not too familiar with valgrind yet so excuse a potentially dumb question.
I'm trying to fix an issue in our code base that valgrind reported as
'Conditional jump or move depends on uninitialised value(s)'. In particular I
have a hard time understanding what the exact item is that's bein
On 6/15/2024 10:38 AM, Thomas Wollenzin wrote:
Hi,
I'm not too familiar with valgrind yet so excuse a potentially dumb
question.
I'm trying to fix an issue in our code base that valgrind reported as
'Conditional jump or move depends on uninitialised value(s)'. In
particular I have a hard ti
Hi,
Re-run with the *--track-origins=yes *flag enabled and it will give you
more detail about where the uninitialized value comes from. (That option
isn't on by default because it makes Valgrind run more slowly.)
Nick
On Sun, 16 Jun 2024 at 06:13, Thomas Wollenzin wrote:
> Hi,
>
> I'm not too
Is there a way to have Valgrind tell me what type exactly has the
uninitialised field or at best break at the time this exact incident occurs?
For over two decades I have asked for a mode which complains at the
instant that an uninit bit is fetched from memory. The usual excuse
of valgrind impl
Also note that malloc()+memset() can choose byte values other than 0;
.
A value such as 0xA5 can increase visual effectiveness of memory dumps.
Also note that there is a feature of glibc malloc() such that the shell
environment variable MALLOC_PERTURN_=NNN (note the trailing underscore)
MALLO
On 15-06-24 17:38, Thomas Wollenzin wrote:
Hi,
I'm not too familiar with valgrind yet so excuse a potentially dumb
question.
I'm trying to fix an issue in our code base that valgrind reported as
'Conditional jump or move depends on uninitialised value(s)'. In
particular I have a hard tim
