Re: [Valgrind-users] Conditional jump or move depends on uninitialised value(s)

[tom f. <tf...@al...>]

Burlen Loring <bur...@ki...> writes:
> Hi all,

Hi Burlen!  Hope all is well.

> Valgrind identifies uninitialized memory when it's used in a
> conditional. It's very smart and can tell when one uninitialized
> value is assigned to another. I'd like to be able to see is a trace
> of all of those assignments that lead to the report starting from the
> reported conditional. Can I?

Try checking out the trunk and using --track-origins=yes.

(Haven't personally tried it yet, just regurgitating info seen here.)

-tom