Re: [Valgrind-users] Uninitialized values with fortran

[Philippe W. <phi...@sk...>]

On Thu, 2013-07-04 at 12:35 -0700, Norman Goldstein wrote:
> I am using valgrind-3.8.1 on Fedora 18, 32 bit x86, and
> am linking fortran libraries to my main C++ code.
> It seems that when malloc'd values end up being initialized
> in fortran code, that this is still tagged by valgrind as
> uninitialized data.  I have worked around (avoided) this problem
> by initializing new memory to 0.  I have seen related posts on the
> net, but am not sure if this is already flagged as a bug, or if I
> am not using valgrind correctly with fortran.
If you know at what place(s) the fortran code is supposed to
initialise the memory, you could use gdb/vgdb, put a break
at this place(s), and then verify that the "v bits" of the
"source memory" used to initialise the target memory are
effectively what is expected (i.e. that the fortran code
is copying "initialised" values to this memory.
This might point at some locations that fortran assumes are
initialised but valgrind did not track such initialisation.

Using --track-origins=yes might also help to pinpoint a possible
error.

Philippe