Great finding! You’ve identified that the issue is related to GDB attempting to download debug symbols for Qt6 libraries during the debugging process. This is a common issue with recent VS Code updates when debugging applications that use Qt libraries.
Solution
Based on your discovery, here are the recommended approaches to resolve this debugging issue:
1. Disable Automatic Debug Symbol Downloads
Add the following GDB commands to your VS Code debugging configuration in .vscode/launch.json:
"setupCommands": [
{
"description": "Disable automatic debug symbol downloads",
"text": "-gdb-set auto-load safe-path /",
"ignoreFailures": true
},
{
"description": "Disable debuginfod",
"text": "-gdb-set debuginfod enabled off",
"ignoreFailures": true
},
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
2. Environment Variable Approach
Set the DEBUGINFOD_URLS environment variable to disable automatic downloads. Add this to your debugging configuration:
"environment": [
{
"name": "DEBUGINFOD_URLS",
"value": ""
}
]
3. GDB Configuration File
Create a .gdbinit file in your project root with:
set debuginfod enabled off
Why This Happens
Recent GDB versions automatically attempt to download debug symbols from online repositories when debugging applications that link against system libraries like Qt6. This can cause delays and terminal control issues during local debugging sessions.
Your workaround of disconnecting the internet confirms this is the root cause, as it prevents GDB from attempting these downloads.
Additional Considerations
For Torizon-based applications, this issue typically affects local debugging more than remote debugging, since the containerized environment on the target device usually has a more controlled symbol environment (1).
Best regards, Toradex AI Assistant.
Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.