GDB fails to start when WireGuard VPN is active - network stack interference

[juvf]

Product: CDT
Component: GDB/DSF

Problem:
When WireGuard VPN is active, Eclipse CDT cannot launch GDB with error: "Could not determine GDB version using command: gdb --version"

Key facts:
gdb --version works fine in Eclipse Terminal when WireGuard is active

gdb --version works fine in system command prompt when WireGuard is active

Debugging works perfectly when WireGuard is disabled

Issue occurs only when WireGuard network interface is active

Eclipse seems to use different environment/process context for debugging vs terminal
GDB works in Eclipse Terminal when WireGuard active

GDB works in system cmd when WireGuard active

Debugging fails ONLY when WireGuard active

Issue: Eclipse debugging process context affected by VPN network changes

Steps to reproduce:
Windows 10 + WireGuard active

Eclipse CDT 2024-09 + GDB 16.3 in PATH

Try to debug any C++ project

Get GDB version detection error

Expected:
GDB should work for local debugging regardless of VPN status