From: Richard Henderson <richard.henderson@linaro.org>
To: Matheus Tavares Bernardino <quic_mathbern@quicinc.com>,
qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, bcain@quicinc.com, f4bug@amsat.org,
peter.maydell@linaro.org, tsimpson@quicinc.com,
philmd@linaro.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v3 6/6] Hexagon (linux-user/hexagon): handle breakpoints
Date: Sun, 7 May 2023 07:27:42 +0100 [thread overview]
Message-ID: <db24af2b-86f0-45d2-5dcf-f3fcae1dea4a@linaro.org> (raw)
In-Reply-To: <c287a129dcbe7d974d8b7608e8672d34a3c91c04.1683214375.git.quic_mathbern@quicinc.com>
On 5/4/23 16:37, Matheus Tavares Bernardino wrote:
> This enables LLDB to work with hexagon linux-user mode through the GDB
> remote protocol.
>
> Helped-by: Richard Henderson<richard.henderson@linaro.org>
> Signed-off-by: Matheus Tavares Bernardino<quic_mathbern@quicinc.com>
> ---
> linux-user/hexagon/cpu_loop.c | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2023-05-07 6:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:37 [PATCH v3 0/6] Hexagon: add lldb support Matheus Tavares Bernardino
2023-05-04 15:37 ` [PATCH v3 1/6] gdbstub: only send stop-reply packets when allowed to Matheus Tavares Bernardino
2023-05-04 15:37 ` [PATCH v3 2/6] gdbstub: add test for untimely stop-reply packets Matheus Tavares Bernardino
2023-05-04 15:37 ` [PATCH v3 3/6] Hexagon: add core gdbstub xml data for LLDB Matheus Tavares Bernardino
2023-05-09 19:12 ` Taylor Simpson
2023-05-04 15:37 ` [PATCH v3 4/6] Hexagon (gdbstub): fix p3:0 read and write via stub Matheus Tavares Bernardino
2023-05-04 15:37 ` [PATCH v3 5/6] Hexagon (gdbstub): add HVX support Matheus Tavares Bernardino
2023-05-12 21:34 ` Brian Cain
2023-05-04 15:37 ` [PATCH v3 6/6] Hexagon (linux-user/hexagon): handle breakpoints Matheus Tavares Bernardino
2023-05-07 6:27 ` Richard Henderson [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=db24af2b-86f0-45d2-5dcf-f3fcae1dea4a@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bcain@quicinc.com \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_mathbern@quicinc.com \
--cc=tsimpson@quicinc.com \
/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).