what is the difference of rdbg and gdb stub provided bylibbsp/cpu/shared/comm

[Joel Sherrill]

Till Straumann wrote:
> 
> Joel Sherrill wrote:
> 
> >gregory.menke at gsfc.nasa.gov wrote:
> >
> >
>
> BTW: does anybody use RDBG on PowerPC? 

This I cannot answer.

> I have - it seems quite broken,
> though.
> While some basic things work, others crash the host gdb (making a target
> reboot
> inevitable). Sorry for not being more specific, I'm out of my office.

Eric Valette recently said he had some time to begin to look at this
again and update it to the latest gdb.  It might not happen until
after the holidays.  Specific input will help him.

> After looking at the 'remote-xxx' (gdb) implementation (I wanted to see
> how hard it would
> be to add support for loadable modules), MHO is that some cleanup/rework
> by a real
> gdb expert would do no harm... (I was still using the 'latest
> stable/working' release of
> rtems-gdb [sidenote: the binaries/RPMs distributed by OaR are _not_
> compiled with
> RDBG support!] - has there been any change since?)

Right for gdb 5.2 but the last gdb 5.0-7 RPMs had them. 
The target names are xxx-RTEMS.

It needs work to compile for gdb 5.2.  

I personally would like to see rdbg as a configure time option
rather than a different target name.  Or something that is
enabled if the host passes certain autoconf tests.

> -- Till
> 
> >
> >The other stub is a serial port based gdb stub based upon the
> >standard gdb remote debugging protocol.  Depending upon the
> >target CPU, it may be thread aware in the stub.  For sure, the
> >mips and i386 stubs were modified to do this.  The support is
> >pretty generic and can be easily adapted to other CPUs.
> >
> >
> >
> >>Gregm
> >>
> >>
> >
> >
> >