From mboxrd@z Thu Jan  1 00:00:00 1970
From: John S. Kallal <jskallal@home.com>
To: gdb@sources.redhat.com
Cc: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Subject: Re: Who owns gdbserver? 
Date: Thu, 21 Jun 2001 13:30:00 -0000
Message-id: <01062113504401.01520@CyberMax>
X-SW-Source: 2001-06/msg00177.html

> 
> On a related note, I'm trying to think of a way to eliminate some of the
> crasser code duplication between gdb and gdbserver - or rather, right now
> it's mostly a lack of code duplication, causing gdbserver not to work
> terribly well.  The ideal solution would be to abstract the details of
> managing a Unix inferior via ptrace to the point where I can link the same
> files into gdbserver, but there are of course some intractable issues -
> setting the shared library debugging breakpoint, for instance.  Before I
> begin working on this, does anyone have any thoughts?  Is someone out there
> working on a similar thing before I waste my time?


Currently gdbserver is only build when you go into the gdbserver's directory 
and build it.  I think that you should 1st change gdb's configure/make system
to alway build gdbserver by default on system where gdbserver is
supported.  That way when ever any change to the shared code
base of gdb/gdbserver creates bit rot, the problem will be quickly 
noticed.   

If possible, it would also be nice to to have gdb's 'make check' command 
automaticly run the testsuite on system that support gdbserver and a TCP/IP 
network loopback.  Again this would help detect bit rot in in the code
that is common to both gdb and gdbserver.
 

John S. Kallal