Evaluating valgrind in multiprocess scenarios

CMakeLists.txt

@@ -0,0 +1,10 @@
+cmake_minimum_required (VERSION 2.8.11)
+
+set (CMAKE_BUILD_TYPE Debug)
+# Add -O0 to remove optimizations when using gcc
+set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -O0")
+set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -O0")
+
+add_executable (parent parent.c)
+add_executable (childA childA.c)
+add_executable (childB childB.c)

README

@@ -0,0 +1,6 @@
+RUNNING WITH VALGRIND
+=====================
+
+mkdir -p build
+cd build; cmake ..; make
+valgrind --trace-children=yes --leak-check=full --show-reachable=yes --error-limit=no --log-file=valgrind.log ./parent

childA.c

@@ -0,0 +1,12 @@
+#include <stdio.h>
+#include <string.h>
+#define WELCOME_MSG "Hello, from child A\n"
+
+int main (int argc, char *argv[])
+{
+    char *str = strdup (WELCOME_MSG);
+
+    printf ("%s", str);
+
+    return 0;
+}

childB.c

@@ -0,0 +1,14 @@
+#include <stdio.h>
+
+int main (int argc, char *argv[])
+{
+    int i = 0;
+    printf ("Hello, from child A\n");
+
+    while (i < argc) {
+        printf ("%s\n", argv[i]);
+        i++;
+    }
+
+    return 0;
+}

parent.c

@@ -0,0 +1,34 @@
+#include <stdio.h>
+#include <unistd.h>
+#include <sys/wait.h>
+#include <string.h>
+
+#define PARENT_MEM_LEAK
+
+#define WELCOME_MSG "Hello, World\n"
+
+void launch(char *app)
+{
+    pid_t pid;
+
+    if ((pid = fork()) == 0) {
+        /* child */
+        execl(app, app, NULL);
+        perror ("app spawn failed\n");
+    } else {
+        /* parent, wait for child to exit */
+        int status = 0;
+        waitpid(pid, &status, 0);
+    }
+}
+
+int main( void )
+{
+#ifdef PARENT_MEM_LEAK
+    char *c = strdup (WELCOME_MSG);
+#else
+    char *c = WELCOME_MSG;
+#endif
+    printf ("%s", c);
+    launch ("childA");
+}