From: Peter Maydell <1921092@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1921092] Re: how do i delete this bug?
Date: Wed, 24 Mar 2021 16:08:26 -0000 [thread overview]
Message-ID: <161660210625.19496.49787149668938267.malone@wampee.canonical.com> (raw)
In-Reply-To: 161658153575.32717.2347487454546278840.malonedeb@soybean.canonical.com
In general, you don't need to delete bugs that turn out to be user
error, or edit the description/title; just mark them as 'invalid',
perhaps with a comment about what turned out to be the cause. That
leaves the trail of what was going on for future readers who might be
going down the same path as you.
There are actually a couple of things we should do here in upstream
QEMU:
* we should document the process for using the debugstub with multi-cluster board models like the mps2-an521
* we should check whether we are doing the right/most appropriate thing when the user connects to the debug stub and is only attaching to one 'inferior' -- it sounds from your report like the un-attached inferior is left permanently in the 'stopped' state. Maybe that's what the gdb protocol requires, but it seems a bit unhelpful.
I'm going to update the bug status/text accordingly.
** Summary changed:
- how do i delete this bug?
+ gdbstub debug of multi-cluster machines is undocumented and confusing
** Changed in: qemu
Status: Invalid => Confirmed
** Description changed:
- no bugs here
+ 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
--
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
next prev parent reply other threads:[~2021-03-24 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 10:25 [Bug 1921092] [NEW] qemu-system-arm multi core debug not working Martin Schönstedt
2021-03-24 10:45 ` [Bug 1921092] " Martin Schönstedt
2021-03-24 14:52 ` Martin Schönstedt
2021-03-24 16:08 ` Peter Maydell [this message]
2021-03-24 21:37 ` [Bug 1921092] Re: gdbstub debug of multi-cluster machines is undocumented and confusing Martin Schönstedt
2021-03-25 16:46 ` Peter Maydell
2021-03-25 18:00 ` Martin Schönstedt
2021-04-08 13:37 ` Peter Maydell
2021-05-14 19:04 ` Thomas Huth
2021-05-14 22:32 ` Martin Schönstedt
2021-05-15 9:18 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161660210625.19496.49787149668938267.malone@wampee.canonical.com \
--to=1921092@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).