Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] Fully disentangle gdb and gdbserver
Date: Sun, 24 Feb 2002 17:49:00 -0000	[thread overview]
Message-ID: <20020224204935.A2247@nevyn.them.org> (raw)

We were already moving in the direction of separating GDB and gdbserver's
build processes, so I finished the job.  This patch adds a simplified
"terminal.h" to gdbserver, and a configure.srv which substitutes for the
makefile fragments in config/.  After this patch, gdbserver is completely
self-contained, with the exception of the regformats/ directory.

I think this is the right way to go.  I've no objection to adding further
common code later, as long as we have clearly fixed and documented
interfaces between that common code and gdb/gdbserver.


[Forthcoming from me tonight after this patch, probably:
  - host vs. target signal numbering
  - ptrace (PTRACE_GET*REGS) support, which will bring in
    x86-64, i386 floating-point registers, and S-390 ports
    of gdbserver, bringing us back to all the potentially working
    targets from before I started.
  - Warning cleanup, and then turning on warnings in the gdbserver
    directory.
 These along with my pending MI testsuite patch actually make gdbserver
 start to look good...]

OK to commit this?

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


             reply	other threads:[~2002-02-25  1:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-24 17:49 Daniel Jacobowitz [this message]
2002-02-24 17:55 ` Daniel Jacobowitz
2002-02-24 18:24   ` Andrew Cagney
2002-02-24 18:48     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020224204935.A2247@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox