From: <gnufans@sina.com>
To: gdb@sources.redhat.com
Subject: port gdb to embedded processor:about RSP
Date: Sat, 04 Oct 2003 05:52:00 -0000 [thread overview]
Message-ID: <20031004055219.3245.qmail@vip.sina.com.cn> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
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!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ssboy
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡gnufans@sina.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-10-04
===================================================================
next reply other threads:[~2003-10-04 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 5:52 gnufans [this message]
2003-10-05 21:59 ` Miki Tebeka
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=20031004055219.3245.qmail@vip.sina.com.cn \
--to=gnufans@sina.com \
--cc=gdb@sources.redhat.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