Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] ppc-linux-nat.c AltiVec regs ptrace
Date: Wed, 20 Feb 2002 15:46:00 -0000	[thread overview]
Message-ID: <20020220184649.B7963@nevyn.them.org> (raw)
In-Reply-To: <15476.11279.326712.932158@localhost.redhat.com>

On Wed, Feb 20, 2002 at 06:06:55PM -0500, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
>  > I'm confused.
> 
> Yeah, you are not the only one.
> 
>  > 
>  > On i386, glibc defines PTRACE_GETFPXREGS.  On PowerPC, in current FSF
>  > glibc, sys/ptrace.h does not define anything along these lines at all. 
> 
> OK, I have downloaded glibc 2.2.5, and sysdeps/unix/sysv/linux/sys/ptrace.h
> defines PTRACE_GETFPXREGS.
> 
> Then on my system, I have /usr/include/sys/ptrace.h which also defines it.
> But I think I have an older version of glibc installed.
> 
> What I am not understanding is where the installed file comes from, is
> it the same as sysdeps/unix/sysv/linux/sys/ptrace.h?

The way the glibc build process works is a mess.  Every target has a
list of sysdep directories.  The first matching file is installed.  In
this case, it is sysdeps/unix/sysv/linux/powerpc/sys/ptrace.h.  When
looking for a file in the glibc source, I recommend always getting a
list of all files by that name first.

>  > If there are outstanding patches to glibc, which defines
>  > PTRACE_GETFPXREGS on PowerPC, then they are still mutable.  They should
>  > be updated to a reasonable value.
>  > 
> 
> I think that rather than oustanding patches we may have older versions.
> 
> I see that in glibc2.2.5 the file
> sysdeps/unix/sysv/linux/powerpc/sys/ptrace.h
> doesn't use the values 18 and 19.
> 
> If I determine that the version of glibc I have used is obsolete, then
> I can clean that up. Let me have a look.

Hopefully I've clarified this a little.  And you seem to have found the
file in question.

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


  reply	other threads:[~2002-02-20 23:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 12:21 Elena Zannoni
2002-02-20 12:39 ` Daniel Jacobowitz
2002-02-20 13:07   ` Elena Zannoni
2002-02-20 14:15     ` Daniel Jacobowitz
2002-02-20 14:34       ` Andrew Cagney
2002-02-20 15:07       ` Elena Zannoni
2002-02-20 15:46         ` Daniel Jacobowitz [this message]
2002-02-20 16:28           ` Elena Zannoni
2002-02-20 16:34             ` Daniel Jacobowitz
2002-02-20 18:09               ` Elena Zannoni
2002-02-20 18:57                 ` Daniel Jacobowitz
2002-02-20 20:10                   ` Elena Zannoni
2002-02-20 21:04                 ` Kevin Buettner
2002-02-21  7:33                   ` Elena Zannoni
2002-02-21  7:33 ` Kevin Buettner
2002-02-21  7:39   ` Elena Zannoni
2002-02-21  8:00     ` Daniel Jacobowitz
2002-02-21 13:25   ` Elena Zannoni
2002-02-21 13:46     ` Kevin Buettner

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=20020220184649.B7963@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ezannoni@redhat.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