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
gdb is unable to show threads list while debugging an executable on Zephyr QEMU targets. Instead of full thread list only the one running thread (current thread) is shown.
This is only an issue with the various Zephyr QEMU targets; thread awareness works as expected with the hardware targets I have tested, through OpenOCD.
To Reproduce
Steps to reproduce the behavior:
west build -b qemu_x86 zephyr/samples/philosophers/
After digging through QEMU's gdbserver (gdbstub.c), it appears to me that the "threads" it exposes are a one-to-one relationship with the emulated cores, and not the target's OS threads. As such, a lot of additional infrastructure needs to be built into QEMU for OS/plataform-specific inspection. zephyrproject-rtos/zephyr#57816 might be a relevant discussion.
This is a bit of a bugger right now for debugging integration tests related to threads on anything but Linux since the native_posix target is only supported on Linux. So right now on macos or Windows the only way to get thread awareness when testing is via an actual board (?)
Describe the bug
gdb
is unable to show threads list while debugging an executable on ZephyrQEMU
targets. Instead of full thread list only the one running thread (current thread) is shown.This is only an issue with the various Zephyr
QEMU
targets; thread awareness works as expected with the hardware targets I have tested, throughOpenOCD
.To Reproduce
Steps to reproduce the behavior:
info threads
Expected behavior
A complete list of all program threads shown, preferably with their name and priority.
Impact
This makes it harder to debug highly concurrent applications for issues such as thread synchronization.
Logs and console output
Expected output (example from board
iotdk
):Actual output from
qemu_x86
:Environment
The text was updated successfully, but these errors were encountered: