You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
No QEMU version update (using latest)
No new Native Debug version (using latest)
No new VS Code (using latest, updated today to May version, no change in error)
No updated gdb version
No update in compiler/linker tooling
No code change
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 via file 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:
1-gdb-set target-async on
2-list-features
3-environment-directory "C:\\Users\\Jakob\\Documents\\workspace\\os-series"
4-enable-pretty-printing
5-target-select remote :1234
add symbol table from file "build/userspace/x86_64-unknown-none/debug/helloworld"
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file
C:\Users\Jakob\Documents\workspace\os-series\dist\x86_64\kernel.bin.
Use `info auto-load
python-scripts [REGEXP]' to list them.
Warning: 'set target-async', an alias for the command 'set mi-async', is deprecated.
Use 'set mi-async'.
Debug Console output with manually loading the file later
1-gdb-set target-async on
2-list-features
3-environment-directory "C:\\Users\\Jakob\\Documents\\workspace\\os-series"
4-enable-pretty-printing
5-target-select remote :1234
add symbol table from file "build/userspace/x86_64-unknown-none/debug/helloworld"
Function "isr_common_stub" not defined.
Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
Warning: 'set target-async', an alias for the command 'set mi-async', is deprecated.
Use 'set mi-async'.
warning: No executable has been specified and target does not support
determining executable automatically. Try using the "file" command.
6-thread-info
7-break-insert -f "c:\\Users\\Jakob\\Documents\\workspace\\os-series\\userland\\src\\libc.rs:31"
8-break-insert -f "c:\\Users\\Jakob\\Documents\\workspace\\os-series\\userland\\src\\main.rs:23"
9-break-insert -f "c:\\Users\\Jakob\\Documents\\workspace\\os-series\\kernel\\src\\process.rs:471"
10-break-insert -f "c:\\Users\\Jakob\\Documents\\workspace\\os-series\\kernel\\src\\syscall.rs:18"
No source file named c:\Users\Jakob\Documents\workspace\os-series\kernel\src\process.rs.
No source file named c:\Users\Jakob\Documents\workspace\os-series\kernel\src\syscall.rs.
11-stack-info-depth --thread 1
12-stack-list-frames --thread 1 0 2
13-stack-info-depth --thread 1
14-thread-info
15-stack-list-frames --thread 1 0 2
16-thread-info
17-thread-info
18-stack-info-depth --thread 1
19-stack-list-frames --thread 1 0 2
file dist/x86_64/kernel.bin
20-interpreter-exec console "file dist/x86_64/kernel.bin"
A program is being debugged already.
Are you sure you want to change the file?
(y or n) [answered Y; input not from terminal]
Load new symbol table from "dist/x86_64/kernel.bin"? (y or n) [answered Y; input not from terminal]
Reading symbols from dist/x86_64/kernel.bin...
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file
C:\Users\Jakob\Documents\workspace\os-series\dist\x86_64\kernel.bin.
Use `info auto-load
python-scripts [REGEXP]' to list them.
Remote target doesn't support qGetTIBAddr packet
Remote target doesn't support qGetTIBAddr packet (from interpreter-exec console "file dist/x86_64/kernel.bin")
The text was updated successfully, but these errors were encountered:
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: