Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Michal Ludvig <mludvig@suse.cz>,
	Mark Kettenis <kettenis@kettenis.dyndns.org>
Cc: Andreas Jaeger <aj@SuSE.de>, Andrew Cagney <ac131313@cygnus.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [patch] Add x86-64 target to MAINTAINERS, broken
Date: Mon, 04 Mar 2002 08:40:00 -0000	[thread overview]
Message-ID: <1020304164006.ZM13485@localhost.localdomain> (raw)
In-Reply-To: Michal Ludvig <mludvig@suse.cz> "Re: [patch] Add x86-64 target to MAINTAINERS, broken" (Mar  4,  1:41pm)

On Mar 4,  1:41pm, Michal Ludvig wrote:

> Mark Kettenis wrote:
> > Anyway, I think the attached patch solves the <sys/reg.h> problem.  It
> > shouldn't break your x86-64 target, but I'm not entirely sure.  Can
> > you test it for me?
> 
> And what about including the contents of sys/reg.h directly into 
> x86-64-tdep.h? That should help as well, or not?

You should first ask yourself why <sys/reg.h> is needed in target
dependent (but host independent) code.  As I understand it,
<sys/reg.h> provides the indices by which registers may be found in
the data structures used to communicate the register's contents to/from
ptrace().  It seems to me that this information is of absolutely no
use when building a cross debugger (to x86-64), but is of vital
concern in the implementation of a native debugger.  Therefore,
<sys/reg.h> should included in the appropriate *-nat.c file instead.

Kevin


      reply	other threads:[~2002-03-04 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 18:44 Andrew Cagney
2002-03-01 22:37 ` Andreas Jaeger
2002-03-04  3:13   ` Michal Ludvig
2002-03-04  4:35     ` Mark Kettenis
2002-03-04  4:41       ` Michal Ludvig
2002-03-04  8:40         ` Kevin Buettner [this message]

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=1020304164006.ZM13485@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=aj@SuSE.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@kettenis.dyndns.org \
    --cc=mludvig@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