public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: William Tambe <tambewilliam@gmail.com>, gdb@sourceware.org
Subject: Re: porting gdbserver
Date: Thu, 15 Oct 2020 15:23:34 -0300	[thread overview]
Message-ID: <2e91d8ee-00e0-1fe8-f2f3-9ee483319a70@linaro.org> (raw)
In-Reply-To: <CAF8i9mNFNxKTMKDU0m3=L5th=EcdymXTF-GLBo2WgBznGvQEbg@mail.gmail.com>

Hi,

On 10/15/20 1:34 PM, William Tambe via Gdb wrote:
> Is there an easy to follow documentation or commit that shows how to port
> gdbserver for baremetal ?
> 

I'm afraid there isn't. I suppose you are talking about actually coming 
up with a debugging stub that implements the most minimal set of remote 
protocol packets, right? Not "gdbserver" itself, which is always OS-hosted.

 From the documentation here...

https://sourceware.org/gdb/onlinedocs/gdb/Overview.html#Overview

... it says:

"At a minimum, a stub is required to support the ‘?’ command to tell GDB 
the reason for halting, ‘g’ and ‘G’ commands for register access, and 
the ‘m’ and ‘M’ commands for memory access. Stubs that only control 
single-threaded targets can implement run control with the ‘c’ 
(continue) command, and if the target architecture supports 
hardware-assisted single-stepping, the ‘s’ (step) command. Stubs that 
support multi-threading targets should support the ‘vCont’ command. All 
other commands are optional."

But the above may be stale at this point.


  reply	other threads:[~2020-10-15 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 16:34 William Tambe
2020-10-15 18:23 ` Luis Machado [this message]
2020-10-16  6:25   ` Christo Crause

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=2e91d8ee-00e0-1fe8-f2f3-9ee483319a70@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=gdb@sourceware.org \
    --cc=tambewilliam@gmail.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).