On Sat, 3 Dec 2011 02:18:01 PM Yuri wrote: > On 12/02/2011 19:04, Brad Hards wrote: > > The meaning depends on the context, which you haven't provided. One > > possibility is that you've malloc'd a char foo[51], and are writing > > beyond the bounds of that array, say with a long at foo[48]; > > Error is printed for the malloc call itself. Below in stack is STL > string constructor, like this: std::basic_string<char, > std::char_traits<char>, ... > If writing would have occurred like you suggested, the error would have > been printed for the function where writing was performed. So if you provide detailed information such as the exact trace, we might be able to do something other than guess.
Brad ------------------------------------------------------------------------------ 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
