24.07.2015 19:52, Jan Kiszka wrote:
> gdb expects that the thread ID for c and g-class operations is set to
> the CPU we provide when reporting VM stop conditions. If the stub is
> still tuned to a different CPU, the wrong information is delivered to
> the gdb frontend.
Applied to -trivial, thanks
gdb expects that the thread ID for c and g-class operations is set to
the CPU we provide when reporting VM stop conditions. If the stub is
still tuned to a different CPU, the wrong information is delivered to
the gdb frontend.
Signed-off-by: Jan Kiszka
---
gdbstub.c | 1 +
1 file changed, 1 inse
