[lkml]   [2011]   [Jun]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/5] ptrace: implement PTRACE_SEIZE

On Sat, Jun 18, 2011 at 09:59:38AM +0200, Denys Vlasenko wrote:
> ...unless we plan to introduce PTRACE_O_TRACESTOP (with value 0x00000080)
> which enables PTRACE_INTERRUPT and stop notifications independently
> of PTRACE_SEIZE. Which would be very useful for e.g. strace.

I know you're a big fan of those option flags but I don't really see
the added value in making these behaviors optional rather than keeping
things backward compatible - ie. introducing new event needed to be
gated somehow so the O flags but SEIZE itself serves as a big gate
anyway so I don't see much point in introducing multiple selectable
behaviors. It's not like PTRACE_O_TRACESTOP is gonna make anything
drastically easier or reduce significant amount of overhead.



 \ /
  Last update: 2011-06-18 10:39    [W:0.040 / U:2.372 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site