> > 2008-06-25  Pedro Alves  <pedro@codesourcery.com>
> >
> > 	Use ptid_t.tid to store thread ids instead of ptid_t.pid.
> >
> > 	* remote.c (magic_null_ptid, not_sent_ptid, any_thread_ptid): New
> > 	globals.
> > 	(general_thread, continue_thread): Change type to ptid_t.
> > 	(record_currthread): Take a ptid_t parameter instead of an
> > 	integer.
> > 	(MAGIC_NULL_PID): Delete.
> > 	(set_thread): Take a ptid_t parameter and adjust.
> > 	(set_general_thread, set_continue_thread): New.
> > 	(remote_thread_alive, remote_newthread_step)
> > 	(remote_current_thread, remote_find_new_threads)
> > 	(remote_threads_info, remote_start_remote, remote_vcont_resume)
> > 	(remote_resume_1, remote_wait, extended_remote_create_inferior_1)
> > 	(threadalive_test, remote_pid_to_str)
> > 	(remote_get_thread_local_address): Adjust.
> > 	(_initialize_remote): Initialize magic_null_ptid, not_sent_ptid
> > 	and any_thread_ptid.
>
> Looks OK to me.

Thanks, I've checked this in.

A Thursday 26 June 2008 03:22:32, Daniel Jacobowitz wrote:
> On Wed, Jun 25, 2008 at 11:51:59PM +0100, Pedro Alves wrote:
> > I've tested this extensivelly by talking to a native gdbserver,
> > and native gdbserver with vCont disabled, and then also with a
> > gdbserver with vCont and all thread related packets and fields
> > disabled, to simulate old stubs and stubs that don't support
> > threads at all.
>
> These sound useful for testing.  Any interest in making them command
> line options for gdbserver?

Sure, something like this?

I don't think we should advertize the options in --help, as
this isn't something we want users to be poking with.

>./gdbserver  --disable-packet
Disableable packets:
  vCont         All vCont packets
  qC            Querying the current thread
  qfThreadInfo  Thread listing
  Tthread       Passing the thread specifier in the T stop reply packet
  threads       All of the above

>./gdbserver  --disable-packet=boo
Don't know how to disable "boo".

Disableable packets:
  vCont         All vCont packets
  qC            Querying the current thread
  qfThreadInfo  Thread listing
  Tthread       Passing the thread specifier in the T stop reply packet
  threads       All of the above

>./gdbserver  --disable-packet=vCont :9999 ./gdbserver
Process ./gdbserver created; pid = 20022
Listening on port 9999


You can then put the extra options in the board file, say, in
the standard native gdbserver board file, it could be:
set_board_info 
gdb_server_prog "../gdbserver/gdbserver  --disable-packet=threads"



-- 
Pedro Alves