[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1921092] Re: gdbstub debug of multi-cluster machines is undocumente
From: |
Martin Schönstedt |
Subject: |
[Bug 1921092] Re: gdbstub debug of multi-cluster machines is undocumented and confusing |
Date: |
Wed, 24 Mar 2021 21:37:25 -0000 |
Thanks for the answer,
indeed the second cluster of the board has been halted when I was
starting gdb the "normal" way - not adding the second inferior. In my
own research I did not find out about these inferiors, so I was
wondering why "info threads" did only show one cpu. Maybe gdb could
inform the user about unattached inferiors when using "info threads"
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1921092
Title:
gdbstub debug of multi-cluster machines is undocumented and confusing
Status in QEMU:
Confirmed
Bug description:
Working with Zephyr RTOS, running a multi core sample on mps2_an521 works
fine. Both cpus start.
Trying to debug with options -s -S the second core fails to boot.
Posted with explanation also at: https://github.com/zephyrproject-
rtos/zephyr/issues/33635
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1921092/+subscriptions
- [Bug 1921092] [NEW] qemu-system-arm multi core debug not working, Martin Schönstedt, 2021/03/24
- [Bug 1921092] Re: qemu-system-arm multi core debug not working, Martin Schönstedt, 2021/03/24
- [Bug 1921092] Re: qemu-system-arm multi core debug not working, Martin Schönstedt, 2021/03/24
- [Bug 1921092] Re: how do i delete this bug?, Peter Maydell, 2021/03/24
- [Bug 1921092] Re: gdbstub debug of multi-cluster machines is undocumented and confusing,
Martin Schönstedt <=
- [Bug 1921092] Re: gdbstub debug of multi-cluster machines is undocumented and confusing, Peter Maydell, 2021/03/25
- [Bug 1921092] Re: gdbstub debug of multi-cluster machines is undocumented and confusing, Martin Schönstedt, 2021/03/25