Re: ptrace(2) man page

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx> writes:

> Hello Heiko,
>
> On Wed, Apr 17, 2013 at 1:39 PM, Heiko Carstens
> <heiko.carstens@xxxxxxxxxx> wrote:
>> ...
>> So, what do you think? Should these architecture specific details go
>> into the ptrace(2) man page?
>> Or somewhere else? Like e.g. Documentation/<arch>/ptrace.txt in the kernel?
>> Or maybe an arch specific "sub" man page like e.g. ptrace.<arch>?
>
> I am not sure, mainly because I am not familiar with the extent of the
> architecture-specific variation in ptrace(2). I do see that there is
> just a very little arch-specific detail in the man page (x86, SPARC).
> I am not (yet) sure of the way forward.

Per architecture there would potentially be a few hundred lines of
additional documentation.  For example, the various register sets could
be enumerated and their layout summarized.  And all the
architecture-specific ptrace requests could be explained.

> I have CCed Denys Vlasenko, since in recent times he has done a lot of
> work on this page, and I assume has a lot of familiarity with the
> various arch-specific details. Perhaps he has an opinion.

Denys, do you have an opinion?

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux