valgrind

I'm using pthreads and according to valgrind I am leaking memory, like in valgrind memory leak errors when using pthread_create The top answer says that if you pthread_join all the threads this memory will be reclaimed, but it isn't for me. pthread_t threads[NUM_THREADS]; ... for (i = 0; i < NUM_THREADS; i++) { pthread_create(&threads[i], &attr, Worker, NULL); } ... for (i = 0; i < NUM_THREADS; i++) { pthread_join(threads[i], NULL); } valgrind output ==2707== HEAP SUMMARY: ==2707== in use at exit: 954 bytes in 4 blocks ==2707== total heap usage: 7,717 allocs, 7,713 frees, 79,563 bytes

A couple of months ago I asked this question where I asked why there was a memory leak. Apparently, I forgot a virtual destructor. Now I'm struggling to understand why this is not a memory leak: #include <iostream> #include <vector> #include <memory> using namespace std; class Base{ public: explicit Base(double a){ a_ = a; } virtual void fun(){ cout << "Base " << a_ << endl; } protected: double a_; }; class Derived : public Base{ public: Derived(double a, double b): Base(a), b_{b}{ } void fun() override{ cout << "Derived " << a_ << endl; } private: double b_; }; int main() { vector<unique_ptr

I was following this exercise . This page has instructions to install Valgrind 3.6.1 but this version of Valgrind is not supported by my current Linux kernel version. So, I installed Valgrind 3.11.0 and followed the instructions there after and on running this command: $ valgrind ./ex4 got this error: valgrind: mmap(0x600000, 8192) failed in UME with error 12 (Cannot allocate memory). How to do I fix it? I'm using Ubuntu 14.04 LTS with kernel version 4.4.0 The error which you have encountered is actually a kernel bug, which was fixed in the subsequent versions. More details here: https:/

The following simple code (C++ 11) will run just find on Mac OS and Linux: #include <thread> #include <chrono> #include <iostream> void threadFunction() { for (int cc=0; cc < 10000000; ++cc) { if (cc%1000000 == 0) { std::this_thread::sleep_for(std::chrono::milliseconds(200)); } } } int main(int argc, char **argv) { std::thread threads[10]; for (int tt = 0; tt < 10; ++tt) { threads[tt] = std::thread(threadFunction); } // Wait for the threads to complete for (int tt = 0; tt < 10; ++tt) { printf("About to join %d\n", tt); std::cout.flush(); threads[tt].join(); printf("Joined %d\n", tt); std::cout

Is there any option for enabling no memory management in gcc while compiling? Main points on using Valgrind while debugging C code compiled with GCC: Compile your code using -O0. In some relatively rare cases (e.g. inline assembly) you may need -O1. Never use higher optimisation levels. The compiler will mangle your code so much that it can make your life impossible. Variables can disappear completely, functions can go mysteriously away as they get inlined, loops become unrolled and so on. Basically with anything other than -O0 you run the risk that the executable code will bear little