From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH for-6.0 0/2] document gdbstub debugging of multicore machines
Date: Wed, 31 Mar 2021 12:25:40 +0100 [thread overview]
Message-ID: <87sg4bo98l.fsf@linaro.org> (raw)
In-Reply-To: <20210325175023.13838-1-peter.maydell@linaro.org>
Peter Maydell <peter.maydell@linaro.org> writes:
> The way gdb and our gdbstub handle multicore and multicluster
> machines is not very obvious. This patchset adds some documentation
> of how to do it. In particular it gives the necessary runes
> for how to get gdb to work with machines which have multiple
> clusters of heterogenous CPUs (that's the sifive_u board, some
> of the MPS2/MPS3 boards, and the Xilinx one).
>
> I don't think there's any way for the stub to tell gdb
> "I have 2 inferiors, attach to both of them", unfortunately,
> so the user has to manually connect to them. (We should talk
> to the gdb folks to confirm that and perhaps suggest protocol
> enhancements. For 6.0, at least let's document the current state
> of affairs.)
Queued to for-6.0/fixes-for-rc2, thanks.
--
Alex Bennée
prev parent reply other threads:[~2021-03-31 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 17:50 [PATCH for-6.0 0/2] document gdbstub debugging of multicore machines Peter Maydell
2021-03-25 17:50 ` [PATCH for-6.0 1/2] docs/system/gdb.rst: Add some more heading structure Peter Maydell
2021-03-25 17:50 ` [PATCH for-6.0 2/2] docs/system/gdb.rst: Document how to debug multicore machines Peter Maydell
2021-03-25 18:17 ` [PATCH for-6.0 0/2] document gdbstub debugging of " Philippe Mathieu-Daudé
2021-03-31 11:25 ` Alex Bennée [this message]
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=87sg4bo98l.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).