-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to attach: Remote target doesn't support qGetTIBAddr packet #431
Comments
Please post the device console with full debug output (there are two options in launch config for that which are by default turned off) to see when the message from GDB is parsed an what it looks like. |
Sure, I assume you mean options "printCalls" and "showDevDebugOutput"? This gives
|
In my blog a commenter gave a solution: https://jakobbr.eu/2024/06/02/remote-target-doesnt-support-qgettibaddr-packet/ |
Thanks @merskip! |
Using GNU gdb (GDB) 14.2
My setup is connecting to qemu as remote target with pretty standard settings.
Since 1 week ago, suddenly* I get following error message popup when connecting to the qemu gdb server:
Failed to attach: Remote target doesn't support qGetTIBAddr packet (from target-select remote :1234)
I wrote "suddenly" because I did not knowingly change anything related to this setup:
I have absolutely no clue why this appears now and what did impact this.
I found out that when I comment
"executable": "dist/x86_64/kernel.bin",
, the debugger starts normally. However, then I am obviously missing the debug symbols. Loading it later viafile dist/x86_64/kernel.bin
throws the error on the console, but then it works fine. But this is of course very inconvenient. It doesnt not work to put the file command in .gdbinit, this leads to the same error on startup.Debug Console output with error:
Debug Console output with manually loading the file later
The text was updated successfully, but these errors were encountered: