Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS

David Miller wrote:

From: supriya kannery <[email protected]>
Date: Fri, 27 Oct 2006 12:50:29 +0530

I checked in gdb and ltrace code. None of them are using PPC_PTRACE* options to get register values. Man page also doesn't mention these options. Once this is fixed, these options could be added to man page also.

Irrespective of whether we fix this, documentation of these options in manpage will clarify its usage I guess.

Yep.  Are the no current users at all?  That's strange...

David,
I guess the reasons for its less (or no) usage could be
1. These options are not documented in manpage
2. The usage is different from the general format of ptrace

3. These are used for copying all the registers. Most applications will require data from a single addr/register at a time and can get this data from a specific register/address using PEEKTEXT or POKETEXT.

We could align these options with the general format of ptrace and then document in manpage mentioning the relevant kernel version

(like what we have for PTRACE_O_TRACESYSGOOD in which kernel version is mentioned)

PTRACE_O_TRACESYSGOOD (since Linux 2.4.6)

Thanks, Supriya



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
    • From: supriya kannery <[email protected]>
  • Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
    • From: David Miller <[email protected]>
  • Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
    • From: supriya kannery <[email protected]>
  • Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
    • From: David Miller <[email protected]>

• Prev by Date: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
• Next by Date: Re: reserve memory in low physical address - possible?
• Previous by thread: Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
• Next by thread: Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]