On 03/10/11 16:04, Andrew Cooper wrote: > Is there a useful location to put an FAQ/equiv stating that an apparent > error in __GI_strlen might suggest that you are not working with NULL > terminating strings? Google was no use which is why I emailed the list.
It's kind of valgrind 101 really - read what the error report says and consider what memory that routine will be reading, and where valgrind says that memory was allocated. I mean if valgrind says that strlen is reading 0 bytes beyond the end of a block allocated at a given location then it's a pretty good bet that the nul terminator was missing on a string and it ran off the end. Tom -- Tom Hughes ([email protected]) http://compton.nu/ ------------------------------------------------------------------------------ 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. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
