Re: gdbserver (was Re: parcelling up struct gdbarch)

[Daniel Jacobowitz <dmj+@andrew.cmu.edu>]

On Tue, Jul 17, 2001 at 01:00:36PM -0400, Andrew Cagney wrote:
> > 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.

How so?  It seems to me to be a much simpler problem, instead.  It
means that gdbserver needes target_signal_to_host and friends, which is
much easier.  If, that is, we change documentation and gdbserver rather than
remote.c.

In fact I'll submit a patch for this later today.  Would you like me to
separate the code out of target.c and share it between gdb and
gdbserver, or just duplicate it?  It sounds to me that we want to
separate gdbserver further, along better-defined boundaries, so
duplicating it and documenting it would be the way to go.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer