From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Fabrice Gautier <gautier@email.enst.fr>
Cc: Daniel Jacobowitz <dmj+@andrew.cmu.edu>, jtc@redback.com, gdb@sources.redhat.com
Subject: Re: gdbserver (was Re: parcelling up struct gdbarch)
Date: Tue, 17 Jul 2001 10:00:00 -0000
Message-id: <3B546F34.6030207@cygnus.com>
References: <3B536B0C.3060908@cygnus.com> <20010716154024.A9181@nevyn.them.org> <20010717012923.F61A.GAUTIER@email.enst.fr>
X-SW-Source: 2001-07/msg00208.html

> In the meantime i already have a question:
> 
> In the current gdbserver, when a new pthread is created, gdbserver sends
> a T packet and the host gdb receive a SIGPWR signal. And i have to type
> c to continue.
> 
> I guess gdbserver must send a T packet when a trhead is created so that
> gdb knows about it, so im' wondering how to do so that gdb doesn't stop
> everytime a new thread is created ?


FYI,

remote.c assumes that the target is sending back signals encoded as 
GDB's ``enum target_signal''.  This contradicts the documentation which 
says that the target sends back signals in a target dependant way.  More 
doco to fix.

Daniel,

This is a similar problem as for registers.

	Andrew