Fix documentation of initCommands for gdb attach configuration

They are sent _after_ attaching, much like for `gdbtarget` configurations.

Author: cwalther

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Change Log
 
+## Unreleased
+
+- Fixes [cdt-gdb-adapter `#432`](https://github.com/eclipse-cdt-cloud/cdt-gdb-adapter/issues/432): Incorrect documentation of `initCommands`.
+
 ## 2.6.0
 
 - Update to cdt-gdb-adapter [v1.6.0](https://github.com/eclipse-cdt-cloud/cdt-gdb-adapter/releases/tag/v1.6.0)

README.md

@@ -35,7 +35,7 @@ Launch and attach configuration settings that can be used with the `gdb` debugge
 | `verbose` | x | x | `boolean` | Produce verbose log output. |
 | `logFile` | x | x | `string` | Absolute path to the file to log interaction with GDB.|
 | `openGdbConsole` | x | x | `boolean` | *(UNIX-only)* Open a GDB console in your IDE while debugging. |
-| `initCommands` | x | x | `string[]` | List of GDB commands sent before attaching to inferior. |
+| `initCommands` | x | x | `string[]` | List of GDB commands sent after attaching to inferior before running/continuing. |
 
 
 ### `gdbtarget` Debugger Type

package.json

@@ -223,7 +223,7 @@
               },
               "initCommands": {
                 "type": "array",
-                "description": "List of GDB commands sent before attaching to inferior.",
+                "description": "List of GDB commands sent after attaching to inferior before continuing.",
                 "items": {
                   "type": "string"
                 },