Dominique Pelle wrote:
> On 8/4/07, Peter Cech <[EMAIL PROTECTED]> wrote:
> > Without that it's hard to tell whether the accesses to
> > uninitialized memory actually (can) result in an incorrect behavior.
> > That's because valgrind operates on rather low level and cannot see
> > if the uninitialized values really influence the program flow or if a
> > higher level logic of the program prevents them to spread further.
> > In short: We need a human to have a look at the code ;-)
>
> 100% agreed. I understand that of course, but accessing uninitialized
> values is generally very suspicious. I will try to debug and see why
> (not simple at first sight) but anybody with access to valgrind can
> reproduce it easily.
Quite often these things are harmless. But one of them can be a real
bug, so we need to avoid them all to find the harmful one.
On some systems with ECC memory reading uninitialized memory can
actually cause a crash.
--
>From "know your smileys":
:-{} Too much lipstick
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
