Changed default GDB extension as I use CCLS language server

and it wasn't playing nice with Microsoft C++/C extension
I think CCLS + Native Debug gives a better experience

.vscode/extensions.json

@@ -1,3 +1,3 @@
 {
-    "recommendations": ["ms-vscode.cpptools"]
+    "recommendations": ["webfreak.debug"]
 }

.vscode/launch.json

@@ -2,24 +2,12 @@
     "version": "0.2.0",
     "configurations": [
       {
-        "name": "g++ build and debug active file",
+        "type": "gdb",
-        "type": "cppdbg",
         "request": "launch",
-        "program": "${workspaceFolder}/build/bin/demo",
+        "name": "Launch Program",
-        "args": [],
+        "target": "${workspaceFolder}/build/bin/demo",
-        "stopAtEntry": false,
         "cwd": "${workspaceFolder}",
-        "environment": [],
+        "valuesFormatting": "parseText"
-        "externalConsole": false,
-        "MIMode": "gdb",
-        "setupCommands": [
-          {
-            "description": "Enable pretty-printing for gdb",
-            "text": "-enable-pretty-printing",
-            "ignoreFailures": true
-          }
-        ],
-        "preLaunchTask": "Build"
       }
     ]
 }

README.md

@@ -11,7 +11,7 @@ Using a PC simulator instead of an embedded hardware has several advantages:
 ## Requirements
 This project is configured for VSCode and only tested on Linux, although this may work on OSx or WSL. It requires a working version of GCC, GDB and make in your path.
 
-To allow debugging inside VSCode you will also require the C/C++ Tools extension [Extension](https://code.visualstudio.com/docs/languages/cpp) or other suitable debugger.
+To allow debugging inside VSCode you will also require a GDB [extension](https://marketplace.visualstudio.com/items?itemName=webfreak.debug) or other suitable debugger.
 
 * **SDL** a low level driver library to use graphics, handle mouse, keyboard etc.