Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Miki Tebeka" <mikit@zoran.co.il>
To: <gnufans@sina.com>, <gdb@sources.redhat.com>
Subject: RE: port gdb to embedded processor:about RSP
Date: Sun, 05 Oct 2003 21:59:00 -0000	[thread overview]
Message-ID: <HGEOJOCIOKDJGKFDEIBAOENOCDAA.mikit@zoran.co.il> (raw)
In-Reply-To: <20031004055219.3245.qmail@vip.sina.com.cn>

Hello,

>	My current plan is to port gdb to a 8-bit embedded
>processor with a new,instead of directly communicating with the
>processor,our gdb will communicate with an emulator.Now suppose
>the BFD has been successfully ported,I am still wondering about
>what in detail I need to do with the remote debugging part.In some
>documents,I have seen some ones
>say it is a must to implement the GDB RSP(remote serial
>protocol),so how in detail I can do to implement it,which files of
>what functionality I must create or modify?  Waiting for help! Thanks!
We do the same here and use a "proxy" GDBInterface which can communicate
with the
simulator (via pipes) or with the hardware (via COM port).

It's just like porting to a new arch, only the "child_create_inferior"
function either
launches the simulator or opens a connection to the hardware.
(Note that we're using a old gdb, things might be different in newer
versions)

HTH.

Bye.
----------------------------------------------------------------------------
-
Smile, damn it, smile.

lambda msg: {
        'name' : 'Miki Tebeka',
        'email' : 'mikit@zoran.co.il',
        'url' : ' http://www.cs.bgu.ac.il/~tebeka',
        'quote' : 'The only difference between children and adults is the
price of the toys'
}[msg]


      reply	other threads:[~2003-10-05 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04  5:52 gnufans
2003-10-05 21:59 ` Miki Tebeka [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=HGEOJOCIOKDJGKFDEIBAOENOCDAA.mikit@zoran.co.il \
    --to=mikit@zoran.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=gnufans@sina.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