Re: [rfc] Fix qC handling in gdbserver

[Daniel Jacobowitz <drow@false.org>]

On Wed, May 02, 2007 at 06:16:28PM +0200, Markus Deuling wrote:
> Hi,
> 
> Daniel Jacobowitz wrote:
> > GDB is opening /proc/pid on the _local_ machine.  That's silly.
> > gdbserver is usually running on a remote machine; it's only on the
> > local machine during native testing.  The testcase fails because info
> > proc only works for native targets.
> 
> thank you again for your input. The patch attached disables 
> gdb.base/info-proc.exp
> for remote targets.
> 
> Is this ok?
> 
> ChangeLog:
> 	* gdb.base/info-proc.exp: Check is_remote.

Yes, this is OK.  It's a little silly since the user can still type
"info proc" and will get garbage, but we don't need to fix that now.

> Btw,
> shall I rework the qC-Patch () and remove the space? Like

Yes please!

> ? Would that be ok for mainline? I wonder why the manual contains qC packets
> while gdb does not? Is this a new feature or one that should be removed from 
> manual rather?

GDB contains support for it; gdbserver doesn't use it, but other
remote stubs do.  For instance, I think RedBoot does.

-- 
Daniel Jacobowitz
CodeSourcery