Ross Boylan <[email protected]> writes: > When I run a test program with leak-check, the first error is > ==14820== Use of uninitialised value of size 4 > ==14820== at 0x40F6841: (within /usr/lib/libstdc++.so.6.0.10) > ==14820== by 0x40FE394: std::ostreambuf_iterator<char, std::char_traits<ch > ar> > std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char > > > >::_M_insert_int<unsigned long>(std::ostreambuf_iterator<char, std::char_ > tra\ > its<char> >, std::ios_base&, char, unsigned long) const (in /usr/lib/libstdc+ > +.so.6.0.10) [snip] > ==14820== Conditional jump or move depends on uninitialised value(s) > ==14820== at 0x40F684A: (within /usr/lib/libstdc++.so.6.0.10) [snip] > First question: why isn't it telling me where the uninitialised value is? Or > is it?
The unitialized value is being utilized in libstdc++; looks like it didn't have debugging information for it, but other places in the stack it does... maybe the debug information in your libstdc++ is incomplete? > The program is compiled with g++ 4.3.2 with -O0 -g, valgrind 3.3.1 on Debian > GNU/Linux Lenny with 32 bit AMD Athlon chip. You'll likely find the report to be much more useful if you upgrade to 3.4.1 and use the --track-origins flag. -tom ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
