Hi, not much to worry about. For some reason on your system environment variable MALLOC_CHECK_ is set to 1. This will cause glibc to spit out warning on all (potential) memory leaks in darktable or its libraries. Most user won't see this as they have MALLOC_CHECK_ not set.
At some point we should have a look those warnings and debug them. If the message annoys you, just start darktable with MALLOC_CHECK_= /opt/darktable/bin/darktable Ulrich Am 29.10.2012 08:47, schrieb Roumano: > Hi, > > Sorry Nop, still some "free() invalid pointer"when i went to darkroom > mode (but can't Always reproduce) : > > ls -ald /opt/darktable/ > ls: cannot access /opt/darktable/: No such file or directory > > sudo make install > /opt/darktable/bin/darktable : > *** glibc detected *** /opt/darktable/bin/darktable: free(): invalid > pointer: 0x00000000022dbf20 *** > *** glibc detected *** /opt/darktable/bin/darktable: free(): invalid > pointer: 0x00000000023388e0 *** > *** glibc detected *** /opt/darktable/bin/darktable: free(): invalid > pointer: 0x000000000233ad20 *** > ------------------------------------------------------------------------------ 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
