This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: Delete remote VxWorks RDB support?
- From: Don Bowman <don at sandvine dot com>
- To: 'Andrew Cagney ' <ac131313 at redhat dot com>, "'gdb at sources dot redhat dot com '" <gdb at sources dot redhat dot com>, Don Bowman <don at sandvine dot com>
- Date: Sat, 3 May 2003 12:16:41 -0400
- Subject: RE: Delete remote VxWorks RDB support?
From: Andrew Cagney
>Hello,
>I found this gem, added 10-May-01, in gdb/TODO:
>> Obsolete the protocols:
>>
>> RDB?
>>
>> ``As of version 5.3, WindRiver has removed the RDB server (RDB
>> protocol support is built into gdb).'' -- Till.
>See: WDB support for the vxWorks target
>http://sources.redhat.com/ml/gdb/2001-05/msg00041.html
...
we are still using RDB & Sandvine. Not sure how many other
people still use it. VxWorks is something people don't update the
core of too rapidly. VxWorks 5.3 is basically the same as VxWorks 5.2.
RDB is not actually removed from 5.3, its just not configured on
by default.
Our reason for using RDB was there was no WDB support in the standard gdb
distribution, and we'd switched to gcc 3 stream, which windriver-supplied
gdb (4.13 I think) didn't understand the debug format of at all for C++.
I suspect most people using vxworks are also using the windriver-supplied
versions of gdb/gcc, which are (as of a couple of years ago), using WDB.