> I suggest you to try valgrind 3.4 (or 3.4.1) with a flag > --track-origins=yes. This will give more informative reports.
--track-origins=yes is useful for making sense of uninitialised value errors, but not for the error shown, which is an addressing error. > > ==9629== Invalid read of size 4 > > ==9629== at 0x43DE2D: > > Pattern::sendSequence(std::_Rb_tree_iterator<std::pair<unsigned const, > > std::string> >) (DataPattern.cpp:168) > > ==9629== by 0x43DFC5: Pattern::bottomSearchAlgorithm() > > (DataPattern.cpp:136) ==9629== by 0x43E011: > > Pattern::handle(std::string const&, unsigned) (DataPattern.cpp:125) > > : > > : Look carefully at the complete error here. Does it have a second stack trace, starting "Address xxxxx is nnn bytes before/after a block of size mmm alloc'd at" ? If you can find that text, it will help explain what the problem is. J ------------------------------------------------------------------------------ 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
