Feel free ;) Am 29.10.2012 19:29, schrieb Mikko Rasa: > Uh, no, those messages have nothing to do with memory leaks. "free(): > invalid pointer" means that free got a pointer that was already freed > earlier, or wasn't malloced at all. If detected, glibc will simply > ignore such pointers, but don't lull yourself into a false sense of > security - the real danger are the potential cases that are _not_ > detected. Depending on exactly how the code is misbehaving, it may end > up freeing memory that shouldn't have been freed yet, or it may try to > free a pointer to an unmapped region, causing a hard segfault. > > Any memory errors like this should be taken seriously and solved > immediately before they have a chance to fester, not "at some point". > As Jesper already pointed out, valgrind is a good tool for finding out > exactly what's going wrong. > > Mikko >
------------------------------------------------------------------------------ The Windows 8 Center - In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
