From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stan Shebs <shebs@cygnus.com>
To: Hendrik.Ruijter@axis.com
Cc: gdb-patches@cygnus.com
Subject: Re: Remote target in gdb 4.17 ecos
Date: Thu, 01 Apr 1999 00:00:00 -0000
Message-ID: <199903092026.MAA11731@andros.cygnus.com>
References: <36E521EA.62AD1C53@axis.com>
X-SW-Source: 1999-q1/msg00069.html
Message-ID: <19990401000000.3hIH_XRkgaRSuNBzOhqukZVMZFPUyCvxESiYq2KPAps@z>

   Date: Tue, 09 Mar 1999 14:28:10 +0100
   From: Hendrik Ruijter <Hendrik.Ruijter@axis.com>

   I have implemented a gdb-stub for our hw architecture.
   A colleague is at present evaulating gdb in ecos and
   it lead to some confusion. I use standard(?) gdb 4.17
   on the host side with the serial protocol described in
   remote.c. However, the gdb-stub within ecos defines a
   different protocol, e.g. Hc-1 is obsolete according to
   my colleague.

GDB 4.17 is nearly a year old; we've recently added some extensions to
the remote protocol to support eCos.  The 4.17+ release that is part
of the eCos toolset on sourceware.cygnus.com includes these extensions
as well, and they are in the upcoming 4.18 release as well.

   Do you intend to develop gdb in another direction from
   4.17 on? Is there any standard gdb x.yz?

I'm not clear on what you're getting at.  If you mean "will the
remote protocol change", then the answer is yes, but we do expect
to extend it in a backward-compatible way.

   Is there any
   documentation on the differences between different 4.17
   implementations?

The gdb/NEWS file is the normal summary of user-visible changes
to GDB.  Releases made by Cygnus usually have a separate set of
release notes.  If these are insufficiently detailed, then you
can send questions to bug-gdb, or ecos-discuss if you need more
eCos detail, or gdb@cygnus.com if it touches on GDB development.

							Stan