From: Stafford Horne <shorne@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: Stafford Horne via Gdb-patches <gdb-patches@sourceware.org>,
Openrisc <openrisc@lists.librecores.org>
Subject: Re: [PATCH 0/5] OpenRISC Linux Native and GDBServer Support
Date: Thu, 21 Oct 2021 06:15:09 +0900 [thread overview]
Message-ID: <YXCG3VDoltpV7i5t@antec> (raw)
In-Reply-To: <87ee8fv9ql.fsf@tromey.com>
On Wed, Oct 20, 2021 at 12:20:34PM -0600, Tom Tromey wrote:
> >>>>> ">" == Stafford Horne via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> >> Hello,
> >> As I have been working on the OpenRISC glibc port over the last few years now I
> >> have had the need to have Linux native debugging. At first I started with the
> >> gdbserver, but quickly grew out of that and just settled on running gdb native
> >> on the platform.
>
> I read through these and it seemed basically ok to me. I sent one
> little nit. I don't think it needs re-review if you want to fix that.
Thanks for reviewing. I will give it a day or two for more comments before
pushing upstream.
-Stafford
prev parent reply other threads:[~2021-10-20 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 12:47 Stafford Horne
2021-09-13 12:47 ` [PATCH 1/5] gdb: or1k: implement gdb server Stafford Horne
2021-10-20 17:33 ` Tom Tromey
2021-10-20 21:17 ` Stafford Horne
2021-09-13 12:47 ` [PATCH 2/5] gdb: or1k: fixup linux regcache comment Stafford Horne
2021-09-13 12:47 ` [PATCH 3/5] gdb: or1k: add generated linux descriptor file Stafford Horne
2021-09-13 12:47 ` [PATCH 4/5] gdb: or1k: add native linux support Stafford Horne
2021-09-13 12:48 ` [PATCH 5/5] gdb: or1k: add single step for linux native debugging Stafford Horne
2021-10-20 18:20 ` [PATCH 0/5] OpenRISC Linux Native and GDBServer Support Tom Tromey
2021-10-20 21:15 ` Stafford Horne [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=YXCG3VDoltpV7i5t@antec \
--to=shorne@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=openrisc@lists.librecores.org \
--cc=tom@tromey.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 read-only IMAP folder(s) and NNTP newsgroup(s).