Re: ptrace(PTRACE_SYSCALL) and data field

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

 



On Mon, Mar 30, 2009 at 12:34 PM, Roland McGrath <roland@xxxxxxxxxx> wrote:
>> On Mon, Mar 30, 2009 at 11:35 AM, Roland McGrath <roland@xxxxxxxxxx> wrote:
>> > All of the "resuming" ptracer requests treat the data argument the same.
>> > Those are PTRACE_CONT, PTRACE_SYSCALL, PTRACE_*STEP, PTRACE_SYSEMU*.
>> > The data argument is either 0 or a signal number.
>> > The addr argument is ignored by all these.
>>
>> Thanks for jumping in Roland.
>>
>> So, for PTRACE_SYSCALL, the sameantics are like PTRACE_CONT, that is,
>> it is interpreted as a signal to be sent to the child.  Right?
>
> For all those requests, yes.

Hmmm.  The existing man page includes this text:

       PTRACE_SYSEMU, PTRACE_SYSEMU_SINGLESTEP (since Linux 2.6.14)
              ...
              (addr and data are ignored; ...

which according to what you've said (and also according to my reading
of the source), is wrong.  Correct?

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
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