On 22/07/14 10:21, quentin.li wrote: > I use Codeblocks create a project to do some device operations in > my code, > and find that if I use "-static" as linker option, memory leak of > the executable file create by Codeblocks won't be detected by valgrind. > Like the memory I malloc that not released by calling free. > But if I close "-static" linker option, all memory leak will be > detected again. > I use cmd: "valgrind --tool=memcheck --leak-check=full .//MyProgram/". > Can anyone kindly tell me why?
http://valgrind.org/docs/manual/faq.html#faq.hiddenbug Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
