Disable memdebug for the allocs done by the app, unless CURLTOOLDEBUG is

defined (which it never is atm).

Now, we can focus on making 'runtests -t [num]' work on all test cases and
we should never leak nor crash.

src/getpass.c

@@ -94,8 +94,8 @@ char *getpass_r(const char *prompt, char *buffer, size_t buflen)
 #endif
 
 /* The last #include file should be: */
-#ifdef CURLDEBUG
+#if defined(CURLDEBUG) && defined(CURLTOOLDEBUG)
-#include "../lib/memdebug.h"
+#include "memdebug.h"
 #endif
 
 char *getpass_r(const char *prompt, char *buffer, size_t buflen)

src/homedir.c

@@ -42,8 +42,8 @@
 
 #include "homedir.h"
 
-#ifdef CURLDEBUG
+#if defined(CURLDEBUG) && defined(CURLTOOLDEBUG)
-#include "../lib/memdebug.h"
+#include "memdebug.h"
 #endif
 
 static

src/main.c

@@ -107,6 +107,9 @@
 
 /* The last #include file should be: */
 #ifdef CURLDEBUG
+#ifndef CURLTOOLDEBUG
+#define MEMDEBUG_NODEFINES
+#endif
 /* This is low-level hard-hacking memory leak tracking and similar. Using
    the library level code from this client-side is ugly, but we do this
    anyway for convenience. */

src/urlglob.c

@@ -35,9 +35,8 @@
 
 #include "urlglob.h"
 
-
+#if defined(CURLDEBUG) && defined(CURLTOOLDEBUG)
-#ifdef CURLDEBUG
+#include "memdebug.h"
-#include "../lib/memdebug.h"
 #endif
 
 typedef enum {