[rfc] Fix qC handling in gdbserver

[Markus Deuling]

Hi,

I had some regressions when running the testsuite on x86 via gdbserver 
and began to look at it. Some FAILs occur because the testcases cannot 
be run via gdbserver (eg. follow fork because we dont have that in 
gdbserver). I'll come up with a patch for the testcases.

When looking at gdb.base/info-proc.exp I found a bug in remote target.

GDB tries to get the initial pid after "target remote :<port>". It does
that by set_thread (-1, 0), which results in a "Hc-1" packet. On 
gdbserver side each Hc packet with '0' or '1' results in E01 packet as 
reply.

Later on remote_current_thread (inferior_ptid); is called which always 
comes back with MAGIC_NULL_PID. The reason for that is the missing 
support for 'qC' packets in gdbserver. Manual says the reply for qC
is 'QC pid'. If no pid returns MAGIC_NULL_PID is taken.

Because of that 'info proc' is broken directly after connecting to
gdbserver (it tries to access /proc/42000), thats why the testcase failes.

This patch adds handling for qC packets in gdbserver and removes the
unnecessary set_thread() call.

Is this ok to commit?

ChangeLog:

	* gdbserver/server.c (handle_query): Add handling for qC
	  packets.
	* remote.c (remote_start_remote): Remove useless set_thread.




-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diff_gdbserver_fix
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20070427/c4aa6a98/attachment.ksh>