Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Jiri Smid <smid@suse.cz>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: x86_64 target files
Date: Thu, 02 Aug 2001 09:43:00 -0000	[thread overview]
Message-ID: <1010802164104.ZM12659@ocotillo.lan> (raw)
In-Reply-To: <s8vg0baa6hb.fsf@naga.suse.cz>

Jiri,

I haven't looked closely at your patch, but one of the things that I
did notice is that your target is not multi-arched.  I am fairly certain
that this will need to be done before your changes will be accepted.

For more information, see

    http://sources.redhat.com/gdb/papers/multi-arch/

Also, I am curious about the reasons for having two *-nat.c files.
I think that x86_64-linux-nat.c is fine, but I noticed that the
presumably more generic x86_64-nat.c still has ptrace() calls in
it.  It seems to me that it may be difficult for other operating
systems (such as those which don't use ptrace()) to make use of
this file.

Kevin


  parent reply	other threads:[~2001-08-02  9:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  7:20 Jiri Smid
2001-08-02  8:39 ` Eli Zaretskii
2001-08-02  9:37   ` Andreas Jaeger
2001-08-02  9:43 ` Kevin Buettner [this message]
2001-08-09 22:53   ` Andrew Cagney
2001-08-09 23:12 ` config/i386/xm-x86_64.h; Was " Andrew Cagney
2001-08-09 23:25 ` configure.host; Was: " Andrew Cagney
2001-08-09 23:41 ` configure.tgt; " Andrew Cagney
2001-08-09 23:57 ` Misc; " Andrew Cagney
2001-08-30  1:35   ` Jiri Smid
2001-08-30  7:39     ` Andrew Cagney
2001-08-30 11:03       ` Andreas Jaeger
2001-08-30 16:53         ` Andrew Cagney
2001-08-31  0:13           ` Andreas Jaeger
2001-08-31  2:00             ` i386 flavors [Was: Re: Misc; Was: [RFA]: x86_64 target files] Andreas Jaeger
2001-08-31 10:39             ` Misc; Was: [RFA]: x86_64 target files Andrew Cagney
2001-08-31 13:12               ` Andreas Jaeger

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=1010802164104.ZM12659@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=smid@suse.cz \
    /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