On 12/02/2011 22:29, Brad Hards wrote: > So if you provide detailed information such as the exact trace, we might be > able to do something other than guess.
I pretty much explained the stack. Well, here it is verbatim: ==27401== Address 0x31d96c0 is 48 bytes inside a block of size 51 alloc'd ==27401== at 0x25A96B: malloc (in /usr/local/lib/valgrind/vgpreload_memcheck-amd64-freebsd.so) ==27401== by 0x79C72A: XAllocator::xalloc(unsigned long) (allocator.h:16) ==27401== by 0x7A21E9: Allocs::xallocator<char>::allocate(unsigned long, void const*) (allocator-for-stl.h:23) ==27401== by 0x7A192E: std::basic_string<char, std::char_traits<char>, Allocs::xallocator<char> >::_Rep::_S_create(unsigned long, unsigned long, Allocs::xallocator<char> const&) (basic_string.tcc:609) ==27401== by 0x7A06AA: std::basic_string<char, std::char_traits<char>, Allocs::xallocator<char> >::_Rep::_M_clone(Allocs::xallocator<char> const&, unsigned long) (basic_string.tcc:631) ==27401== by 0x79F86D: std::basic_string<char, std::char_traits<char>, Allocs::xallocator<char> >::_Rep::_M_grab(Allocs::xallocator<char> const&, Allocs::xallocator<char> const&) (basic_string.h:224) ==27401== by 0x7A934E: std::basic_string<char, std::char_traits<char>, Allocs::xallocator<char> >::basic_string(std::basic_string<char, std::char_traits<char>, Allocs::xallocator<char> > const&) (basic_string.tcc:175) Now I am curious what additional information you can deduce from this stack. Yuri ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
