Dan,

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....

-- Brian

Dan Kegel wrote:
> On Fri, Oct 10, 2008 at 11:11 AM, Brian Wainscott <[EMAIL PROTECTED]> wrote:
>> It has been a while since I've used valgrind much, and have started trying
>> it again lately, but have a LOT of what I believe are bogus error reports
>> about uninitialized variables.  Several I've traced back to obvious
>> initialization statements.  I think the relevant point is that I'm running
>> on an x86_64 system, with 64 bit pointers and 32 bit data, but all the
>> "unitialized value" errors say "size 8"!  But all my data is size 4!
> 
> Perhaps the architecture (not valgrind) does loads of size 8 anyway.
> 
>> Now, this "error" is in the system libraries, and I don't KNOW that the
>> error report is wrong.  But I don't get ANY errors about the usage of junk,
>> or anything else.
> 
> Check out the new valgrind option --track-origins=yes.  It's only
> in the trunk, not in any release yet, but it's the cat's pajamas.
> - Dan


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to