[Breakpoints] Stopping due to fatal error: ArgumentNullException: Value cannot be null. (Parameter 'key')

Environment

• OS and version: Ubuntu 22.04.5 LTS
• VS Code: 1.96.4
• C/C++ extension: 1.23.5
• OS and version of remote machine (if applicable): N/A
• GDB / LLDB version: tried with GDB 12.1 and GDB 16.2

Bug Summary and Steps to Reproduce

Bug Summary:

• If I set a breakpoint, and run my Binary and then stop at the breakpoint, I get the Message:
  Stopping due to fatal error: ArgumentNullException: Value cannot be null. (Parameter 'key')

• and Then I can no longer Step Over or see variables

• NOTE: This was working before, I might have installed a conflicting library or something?
  Steps to reproduce:

1. In this environment...
2. With this config...
3. Do '...'
4. See error...

Debugger Configurations

Launch.json
        {
            "name": "Run test (Linux x64)",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/out/${input:outTestLinux}",
            "args": [],
            "cwd": "${workspaceFolder}"
        },

Debugger Logs

=thread-group-added,id="i1"
GNU gdb (GDB) 16.2
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Warning: Debuggee TargetArchitecture not detected, assuming x86_64.
=cmd-param-changed,param="pagination",value="off"
Stopped due to shared library event (no libraries added or removed)
Loaded '/lib64/ld-linux-x86-64.so.2'. Symbols loaded.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, main () at ../../third_party/pigweed/repo/pw_unit_test/simple_printing_main.cc:22
22	int main() {
Loaded '/lib/x86_64-linux-gnu/libatomic.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libssl.so.3'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libcrypto.so.3'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libgio-2.0.so.0'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libgobject-2.0.so.0'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libglib-2.0.so.0'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libm.so.6'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libresolv.so.2'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libc.so.6'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libpthread.so.0'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libgmodule-2.0.so.0'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libz.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libmount.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libselinux.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libffi.so.8'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libpcre.so.3'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libblkid.so.1'. Symbols loaded.
Loaded '/lib/x86_64-linux-gnu/libpcre2-8.so.0'. Symbols loaded.

Breakpoint 3, (anonymous namespace)::GetAddressWithMediumScore (port=5540, interfaceId=...) at ../../src/lib/address_resolve/tests/TestAddressResolve_DefaultImpl.cpp:84
84	    Inet::IPAddress ipAddress;
Execute debugger commands using "-exec <command>", for example "-exec info registers" will list registers in use (when GDB is the debugger)
Stopping due to fatal error: ArgumentNullException: Value cannot be null. (Parameter 'key')

Other Extensions

No response

Additional Information

No response

Inizia riproducendo il malfunzionamento con la configurazione launch.json fornita e GDB 12.1 o 16.2, fermandoti al breakpoint mostrato nei log. Traccia quindi il percorso di arresto al breakpoint che produce l’ArgumentNullException, poi verifica che, dopo la correzione, l’esecuzione passo-passo e l’ispezione delle variabili funzionino normalmente.