valgrind

I have a lot of possible lost entry from valgrind. What does that mean ? As I am using sqlite and it is well tested. I don't think these are correct entry. What I am doing wrong ? 16 bytes in 1 blocks are possibly lost in loss record 30 of 844 ==23027== at 0x4A05E1C: malloc (vg_replace_malloc.c:195) ==23027== by 0x6525BE: sqlite3MemMalloc (in app_mem.out) ==23027== by 0x63C579: mallocWithAlarm (in app_mem.out) ==23027== by 0x63C904: sqlite3DbMallocRaw (in app_mem.out) ==23027== by 0x6886D6: codeOneLoopStart (in app_mem.out) ==23027== by 0x68A9C8: sqlite3WhereBegin (in app_mem.out) ==23027== by

Does anyone know of memory debugging tools (like Valgrind) for native C++ code under Android NDK? We have a project that uses quite a bit of native code. As hinted in one of the comments for the question, the best approach is to test that code on another environment. We have a separate project that builds in Linux and calls the C/C++ functions we use in our Android code. Once you are at that point, all the nice tools you are used to (gdb, Valgrind, etc.) are available to you. A lot more productive than doing the same thing on the phone (assuming you could even find a good tool). The tricky

I have a process x that I want to check for leaks with valgrind . The problem is that x is run by y , and y in turn is run by z . I can't run x standalone because y and z setup the environment for x , such as environment variables, command line switches, files needed by x etc. Is there any way I can tell valgrind to run on z but to follow any forks it finds and report them too? Is there any way I can tell valgrind to follow any forks but only report on the process named x ? Is there any way I can tell valgrind to attach to already-running process, the way I can do with gdb? I don't know if

I recently encountered my first battle (solved) with heap corruption. On my linux machine at home the culprit code exits without error using valgrind and electric-fence(with gdb). Yet on the windows machine in our lab, I consistently get the heap corruption related error message from VS described in my referenced post. Is it surprising (or at least uncommon) that valgrind and electric fence wouldn't detect such a problem? Someone else mentioned a possibly similar bug that eluded valgrind in a answer here . What might be some reasons why this problem wouldn't be detected by these tools? Is

I ran configure with the following option: ./configure --target=armv5tel CC=arm-linux-gnueabi-gcc --host=i686-linux then ran make I encountered the following error: m_cpuid.S: Assembler messages: m_cpuid.S:40: Error: bad instruction `pushl %ebp' m_cpuid.S:41: Error: bad instruction `movl %esp,%ebp' m_cpuid.S:42: Error: bad instruction `pushl %ecx' m_cpuid.S:43: Error: bad instruction `pushfl' m_cpuid.S:44: Error: bad instruction `pushfl' m_cpuid.S:45: Error: bad instruction `popl %eax' m_cpuid.S:46: Error: bad instruction `movl %eax,%ecx' m_cpuid.S:47: Error: bad instruction `xorl $0x200000,

My intent is to use Clang as a replacement for Valgrind on Windows to find buffer overflows, dynamic memory misuse etc. in C/C++ programs that I've written. I have successfully built Clang following the instructions provided here . I attempted to compile a simple C program with the -faddress-sanitizer option (as specified here ) and the following the error is thrown - gcc.exe: error: unrecognized command line option '-faddress-sanitizer' Using built-in specs. COLLECT_GCC=C:/MinGW/bin/gcc.exe Target: mingw32 Configured with: ../gcc-4.7.0/configure --enable-languages=c,c++,ada,fortran,objc,obj-

my program processes large errors and during development in produces large amount of output on the console. It suffers from memory corruption and I try to use valgrind to locate the error. Unfortunately, i can't find the error messages among the output lines, and they flushing by too fast to cancel execution when they pop up. They have to be there in order to locate the error ( which element does cause the error and so on ). Redirecting then within my program doesn't work, just like piping the output does only redirect the program output, not the valgrind output. Can you give me a hint how to

This question already has an answer here: Segfaults in malloc() and malloc_consolidate() 2 answers My program goes in segmentation faults, and I cannot find the cause. The worst part is, the function in question does not always lead to segfault. GDB confirms the bug and yields this backtrace: Program received signal SIGSEGV, Segmentation fault. 0xb7da6d6e in malloc_consolidate (av=<value optimized out>) at malloc.c:5169 5169 malloc.c: No such file or directory. in malloc.c (gdb) bt #0 0xb7da6d6e in malloc_consolidate (av=<value optimized out>) at malloc.c:5169 #1 0xb7da9035 in _int_malloc (av=