Create DEBUGGER variable

TestFramework/gnustep-tests.in

@@ -517,14 +517,16 @@ proc_test_log ()
 
   if test x"$GSTESTDBG" != x
   then
+    DEBUGGER=`gnustep-config --variable=DEBUGGER`
+    EXT=`gnustep-config --variable=EXEEXT`
     if present "$GSTESTSUM.tmp" "^Failed test:"
     then
       grep '^Failed test:' "$GSTESTLOG.tmp" | sed -e 's/^Failed test:[^:]*:\([0-9][0-9]*\).*/break testStart if testLineNumber==\1/' > "$GSTESTDBG"
-      gdb "./obj/$TESTNAME" -x "$GSTESTDBG"
+      DEBUGGER "./obj/$TESTNAME"EXT -x "$GSTESTDBG"
       rm -f "$GSTESTDBG"
     elif present "$GSTESTSUM.tmp" "^Failed file:"
     then
-      gdb "./obj/$TESTNAME"
+      DEBUGGER "./obj/$TESTNAME"EXT
     fi
   fi
 

config.make.in

@@ -154,6 +154,16 @@ LEX             = lex
 CHOWN           = chown
 STRIP           = strip
 
+# The Windows MSVC toolchain does not support debugging via the default
+# debugger gdb, this is why lldb is used instead.
+# 1. gdb can't read MSVC-compiled executables
+# 2. gdb is distributed with an MinGW environment
+ifeq (@target_os@,windows)
+  DEBUGGER = lldb
+else
+  DEBUGGER = gdb
+endif
+
 INSTALL		= @HOST_INSTALL@
 INSTALL_PROGRAM	= @INSTALL_PROGRAM@
 INSTALL_DATA	= @INSTALL_DATA@

gnustep-config.in

@@ -184,6 +184,10 @@ case "$1" in
               exit 0;;
   --variable=LDFLAGS) echo "@LDFLAGS@"
               exit 0;;
+  --variable=EXEEXT) echo "@EXEEXT@"
+              exit 0;;
+  --variable=DEBUGGER) echo "@DEBUGGER@"
+              exit 0;;
   --variable=GNUSTEP_MAKEFILES) echo "$GNUSTEP_MAKEFILES"
               exit 0;;
   --variable=GNUMAKE) echo "@GNUMAKE@"