All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 1/5] gdb: or1k: implement gdb server
Date: Thu, 21 Oct 2021 06:17:05 +0900	[thread overview]
Message-ID: <YXCHUXYCuee3POqO@antec> (raw)
In-Reply-To: <87mtn3vbwq.fsf@tromey.com>

On Wed, Oct 20, 2021 at 11:33:41AM -0600, Tom Tromey wrote:
> >>>>> ">" == Stafford Horne via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> >> This patch adds gdbserver support for OpenRISC.  This has been used for
> >> debugging the glibc port that in being worked on here:
> 
> >>   https://github.com/openrisc/or1k-glibc/tree/or1k-port-2
> 
> >> Hence the comment about registers definitions being inline with glibc.
> 
> Thanks for the patch.  I had one minor comment.
> 
> >> +#define or1k_breakpoint_len 4
> 
> >> +bool
> >> +or1k_target::low_breakpoint_at (CORE_ADDR where)
> >> +{
> >> +  unsigned int insn;
> >> +
> >> +  read_memory (where, (unsigned char *) &insn, 4);
> 
> Perhaps this ought to use or1k_breakpoint_len here.

Right, I will update that before pushing.

> >> +/* Fetch the thread-local storage pointer for libthread_db.  */
> >> +
> >> +ps_err_e
> >> +ps_get_thread_area (struct ps_prochandle *ph,
> >> +		    lwpid_t lwpid, int idx, void **base)
> >> +{
> 
> Not your problem but it seems like a shame that this exact
> implementation is repeated several times in gdbserver.

I agree.

-Stafford

  reply	other threads:[~2021-10-20 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 12:47 [OpenRISC] [PATCH 0/5] OpenRISC Linux Native and GDBServer Support Stafford Horne
2021-09-13 12:47 ` [OpenRISC] [PATCH 1/5] gdb: or1k: implement gdb server Stafford Horne
2021-10-20 17:33   ` Tom Tromey
2021-10-20 21:17     ` Stafford Horne [this message]
2021-09-13 12:47 ` [OpenRISC] [PATCH 2/5] gdb: or1k: fixup linux regcache comment Stafford Horne
2021-09-13 12:47 ` [OpenRISC] [PATCH 3/5] gdb: or1k: add generated linux descriptor file Stafford Horne
2021-09-13 12:47 ` [OpenRISC] [PATCH 4/5] gdb: or1k: add native linux support Stafford Horne
2021-09-13 12:48 ` [OpenRISC] [PATCH 5/5] gdb: or1k: add single step for linux native debugging Stafford Horne
2021-10-20 18:20 ` [OpenRISC] [PATCH 0/5] OpenRISC Linux Native and GDBServer Support Tom Tromey
2021-10-20 21:15   ` Stafford Horne

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=YXCHUXYCuee3POqO@antec \
    --to=shorne@gmail.com \
    --cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.