From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: gdbserver/{<foo>,<os>,<bar>}.c?; Was: [rfa] gdbserver overhaul
Date: Thu, 18 Oct 2001 12:08:00 -0000 [thread overview]
Message-ID: <20011018150810.A21022@nevyn.them.org> (raw)
In-Reply-To: <3BCF2661.3020304@cygnus.com>
On Thu, Oct 18, 2001 at 02:58:41PM -0400, Andrew Cagney wrote:
> >>Date: Thu, 18 Oct 2001 11:57:40 -0400
> >>From: Andrew Cagney <ac131313@cygnus.com>
> >
> >>>
> >
> >>>> or if it did it couldn't use any of these low-* files right?
> >
> >>>
> >>>
> >>> Sorry, I don't understand this. How is the DJGPP port different from
> >>> any other port in this respect?
> >
> >>
> >>I don't think DJGPP's low/nat interface looks like UNIX's ptrace() or
> >>/procfs so much of the existing low-* code wouldn't be used.
> >
> >
> >That's true, but the low-* files are supposed to be compiled on the
> >target system, not on the host, right? If so, all but one of these
> >low-* files is irrelevant for other platforms as well, right?
>
> Yes. My understanding of DanielJ's cleanup is that it better structures
> (separate os/cpu specific and generic files) the unix low code.
Yes, that's right. Well, more specifically:
- I create a file for each CPU supported, ideally - there may be
multiple variants of this for different OS targets, and I haven't
checked any besides Linux, but I don't think there should be...
- I create a new file, broken out of the monstrous linux target file,
for each supported linux target.
There is little common Unix support code, but there looks as if there
should be more. After some more factoring of architecture-specific
bits, perhaps there will be.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-10-18 12:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 13:15 Daniel Jacobowitz
2001-10-14 18:13 ` Andrew Cagney
2001-10-14 18:44 ` Daniel Jacobowitz
2001-10-16 21:12 ` Andrew Cagney
2001-10-16 21:24 ` Daniel Jacobowitz
2001-10-16 21:09 ` Andrew Cagney
2001-10-16 21:23 ` Daniel Jacobowitz
2001-10-17 4:45 ` Eli Zaretskii
2001-10-17 9:06 ` Andrew Cagney
2001-10-17 10:57 ` Daniel Jacobowitz
2001-10-17 12:34 ` gdbserver/{<foo>,<os>,<bar>}.c?; Was: " Andrew Cagney
2001-10-17 13:39 ` Daniel Jacobowitz
2002-09-27 15:35 ` Andrew Cagney
2002-09-27 15:49 ` Andrew Cagney
2001-10-18 1:11 ` Eli Zaretskii
2001-10-18 9:30 ` Andrew Cagney
2001-10-18 12:36 ` Eli Zaretskii
2001-10-18 11:59 ` Andrew Cagney
2001-10-18 12:08 ` Daniel Jacobowitz [this message]
2001-10-21 4:02 ` Mark Kettenis
2001-10-21 9:15 ` Andrew Cagney
2001-10-17 15:17 ` Daniel Jacobowitz
2001-10-18 14:28 ` Andrew Cagney
2001-10-18 17:06 ` 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=20011018150810.A21022@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--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