valgrind

I am attempting to build massif-visualizer on CentOS 7. Unfortunately I'm having to try to guess at dependencies as they are not all listed in the INSTALL file. So far: yum install git yum install kdelibs-devel extra-cmake-modules \ qt5-qtsvg-devel qt5-qtxmlpatterns-devel \ kf5-kparts-devel kf5-karchive-devel git clone https://github.com/KDE/massif-visualizer cd massif-visualizer mkdir build (cd build && cmake .. && make && make install) Those Qt5 and KF5 packages were added to the yum command largely by trial and error, and some pattern-matching from CMake error messages … but I cannot seem

When I installed WSL for my computer I was very excited to have a more natively supported Linux system rather than using VirtualBox . However I get this error when I try to run it. Is there a reason why? I am happy to give more information as required. --4364:0:aspacem -1: ANON 0038000000-00383d5fff 4022272 r-x-- SmFixed d=0x000 i=25365 o=0 (0) m=0 /usr/lib/valgrind/memcheck-amd64-linux --4364:0:aspacem Valgrind: FATAL: aspacem assertion failed: --4364:0:aspacem segment_is_sane --4364:0:aspacem at m_aspacemgr/aspacemgr-linux.c:1502 (add_segment) --4364:0:aspacem Exiting now. It's definitely

We have a complex program that is working well on heavy duty input (any input actually) with no multithreading implemented. We've implemented multithreading with a threadpool, and given these input parameters I get these results: ( Note : Where I say no errors , it means I've tested with valgrind -v and when I say no memory leaks , it means I've tested it with valgrind --leak-check=full -v ). small_file: Runs successfully with more than 1 workers (threads), no valgrind errors, no memory leaks medium_file: With 1 worker it runs successfully, no errors/memory leaks. With > 1 workers, I get: a.

Is it possible to tell valgrind to ignore some set of libraries? Specifically glibc libraries.. Actual Problem: I have some code that runs fine in normal execution. No leaks etc. When I try to run it through valgrind, I get core dumps and program restarts/stops. Core usually points to glibc functions (usually fseek, mutex etc). I understand that there might be some issue with incompatible glibc / valgrind version. I tried various valgrind releases and glibc versions but no luck. Any suggestions? This probably doesn't answer your question, but will provide you the specifics of how to suppress

Say I have the following program #include <stdio.h> #include <stdlib.h> int main(void) { int * i; if ((i = malloc(sizeof(int) * 100)) == NULL) { printf("EROOR: unable to allocate memory \n"); return -1; } /* memory is allocated successfully */ /* memory is not free'ed but program terminates */ // free(i); return 0; } The above program calls malloc to allocate some memory and does not call free to de-allocate it. And the program terminates without de-allocating the memory. Valgrind clearly detects a memory leak. <snap> ==14209== HEAP SUMMARY: ==14209== in use at exit: 400 bytes in 1 blocks =

I see that valgrind has an ARM7 target, but I find conflicting information on whether valgrind has support for the ARM9. The ARM9 target I am working with is running linux. Has anyone specifically succeeded in using valgrind on an ARM9 target? If so, any pointers you can offer would be helpful, including "how did you build it?". Thanks -z Valgrind runs on ARM-v7 (architecture name), not ARM7 (chip family name). ARM7 is a name of a fairly old chip family (which uses architecture ARM-v4), as is ARM9 (ARM-v5). Are you sure that your chip is an ARM9 and not a Cortex-A9 (which uses the ARM-v7