Hello,
While analyzing a complex C-written database layer with valgrind 3.9.0, I
encounter the following problem in some statement; the called functions
are putting together a database SELECT statement:
...
==17454== Conditional jump or move depends on uninitialised value(s)
==17454==at
==17454== Conditional jump or move depends on uninitialised value(s)
==17454==at 0x5921F10: strchrnul (in /lib/libc-2.11.3.so)
==17454==by 0x58E55D6: vfprintf (in /lib/libc-2.11.3.so)
the involved fuctions are shown below; the statement in question (see below)
is
sprintf
On Mon, 2014-07-28 at 07:11 -0700, John Reiser wrote:
==17454== Conditional jump or move depends on uninitialised value(s)
==17454==at 0x5921F10: strchrnul (in /lib/libc-2.11.3.so)
==17454==by 0x58E55D6: vfprintf (in /lib/libc-2.11.3.so)
the involved fuctions are shown below; the
--db-attach=yes should be considered as (is?) obsolete.
You could instead use --vgdb-error=1 (to just attach when the error is
reported) or better use --vgdb-error=0, put breakpoints
and verify the (un-)definedness of the relevant variables at various
points between their declaration and
