|
From: Dan K. <da...@ke...> - 2008-10-11 02:58:34
|
On Fri, Oct 10, 2008 at 6:17 PM, Brian Wainscott <br...@ls...> wrote: > Thanks -- I'll check that out. My immediate problem is solved, in that I > was able to use an old copy of valgrind (2.2) on an IA32 machine: it > reported SOME uninitialized values (all in some fortran libraries which I've > come to expect as normal). It DID report "Invalid write" which valgrind 3.3 > did NOT report on the x86_64 platform....and fixing that fixed my problem. > I still think there is something suspicious here, but will look into some > of these "uninitialized values" using the --trace-origins option you > mention. But it bothers me that valgrind 3.3 did not detect the invalid > write, which was corrupting my heap, and valgrind 2.2 did.... Could be because the heap is aligned on 16 byte boundaries for 64 bit machines, so there's more slop allowed, as it were... - Dan |