Rename ftldns/debugging -> ftldns/gdb for clarity

Signed-off-by: DL6ER <[email protected]>

Author: DL6ER

docs/ftldns/debugging.md renamed to docs/ftldns/gdb.md

@@ -79,7 +79,7 @@ When set to `yes`, Memcheck keeps track of the origins of all uninitialised valu
 
 You can also combine `valgrind` with `gdb` to get both the memory error detection and the ability to step through the code after a crash (or other unexpected behaviour).
 
-1. Prepare `gdb` as described in [the `gdb` guide](debugging.md).
+1. Prepare `gdb` as described in [the `gdb` guide](gdb.md).
 2. Start `pihole-FTL` in `valgrind` as described above. The `--vgdb=full` option tells `valgrind` to start a GDB server.
 3. Once FTL has started, you can attach `gdb` to the running process using
 

docs/ftldns/valgrind.md

@@ -147,7 +147,7 @@ nav:
         - 'Cache dump': ftldns/cache_dump.md
         - 'Packet dump': ftldns/package_dump.md
         - 'Debugging':
-            - 'gdb': ftldns/debugging.md
+            - 'gdb': ftldns/gdb.md
             - 'valgrind': ftldns/valgrind.md
   - 'Group Management':
     - 'Group Management': group_management/index.md
@@ -283,3 +283,4 @@ plugins:
         'guides/vpn/openvpn/overview.md': guides/vpn/openvpn/index.md
         'guides/misc/tor/overview.md': guides/misc/tor/index.md
         'guides/github/contributing.md': guides/github/index.md
+        'ftldns/debugging.md': ftldns/gdb.md