[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays
From:       Philippe Waroquiers <bugzilla_noreply () kde ! org>
Date:       2016-11-03 6:20:17
Message-ID: bug-371966-17878-ATutcsjnOX () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=371966

--- Comment #5 from Philippe Waroquiers <philippe.waroquiers@skynet.be> ---
(In reply to Carl Ponder from comment #3)
> This "pgfortran" is the PGI Fortran compiler.
> What I'm puzzled about is why valgrind is finding more uninitialized
> array-elements when I compiled with gfortran than with pgfortran, and if I
> use
> 
> pgfortran -O0 -gopt -Mstack_arrays ...
> 
> valgrind doesn't find any uninitialized array-elements at all.
> So this "gdb+vgdb" will show me the valgrind internal tables that keep track
> of what's initialized and what isn't?
The best is to read the manual:
see
http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver
and the section in the memcheck part describing the memcheck specific
monitor commands
http://www.valgrind.org/docs/manual/mc-manual.html#mc-manual.monitor-commands

The manual is (supposed to be) clear/complete and understandable, but
can for sure always be improved (so, file a new bug if something is not clear)

Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]