From: Quality Quorum <qqi@world.std.com>
To: Joachim Geishauser <r38313@email.sps.mot.com>
Cc: gbb <gdb@sources.redhat.com>
Subject: Re: gdb remote debugging
Date: Tue, 02 Oct 2001 06:48:00 -0000 [thread overview]
Message-ID: <Pine.SGI.4.30.0110020937430.1387-100000@world.std.com> (raw)
In-Reply-To: <3BB97BED.1115070C@email.sps.mot.com>
On Tue, 2 Oct 2001, Joachim Geishauser wrote:
> Hi all ,
>
> as far as I know gdb can be used to debug code running on a i.e Coldfire
>
> on a external board.
> Is the code that does the communication between the code running on the
> external board and
> gdb running on the workstation open source?
Yes, there are few stubs in gdb-5.0/gdb directory, there is gdbstubs
project on sourceforge and there are stubs distributed as a part
of eCos and RTEMS. As far as I remember all of them are given to
the public domain or near public domain.
Most files in the gdb-5.0/stub directlory contain a short description
of the protocol.
I tried to make a formal description see my web site at
http://world.std.com/~qqi
> Is there documentation of
> the API for the code
> running on the external board and the external board part of the gdb
> communication available?
> Any feedback is welcomed.
In my experience, however, tweaking is required and it is important
to know what are you doing.
Also, you can invent your own protocol and and extend gdb, it is not a
hard thing to do.
>
> Regards
> Joachim
>
Thanks,
Aleksey
next prev parent reply other threads:[~2001-10-02 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 1:34 Joachim Geishauser
2001-10-02 6:48 ` Quality Quorum [this message]
2003-09-06 7:26 Liu Lijuan
2003-09-06 18:50 ` Daniel Jacobowitz
2003-09-07 1:59 ` Liu Lijuan
2003-09-07 3:50 ` Daniel Jacobowitz
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=Pine.SGI.4.30.0110020937430.1387-100000@world.std.com \
--to=qqi@world.std.com \
--cc=gdb@sources.redhat.com \
--cc=r38313@email.sps.mot.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