[lkml]   [2011]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 03/10] ptrace: implement PTRACE_SEIZE
    On Thursday 19 May 2011 15:17:28, Tejun Heo wrote:
    > But making SEIZE not trigger INTERRUPT and SETOPTIONS without
    > requiring TRACED don't seem too difficult. Jan, would that be enough?
    > Oleg, what do you think?

    UUIC, that opens a race where between SEIZEing and
    SETOPTIONS(O_TRACE FORK|VFORK|EXEC...), the tracee can
    fork/vfork/clone/exec, without the tracer getting the
    nice corresponding PTRACE_EVENT_ events.

    In GDBs case, GDB will want to poke at memory
    right after attaching, to at least read the
    loaded DSO list, so if you can't read tracee
    memory without interrupting it, you won't get much
    benefit from SEIZE not interrupting.
    Not to say other users wouldn't benefit.

    Pedro Alves

     \ /
      Last update: 2011-05-19 21:41    [W:0.020 / U:6.040 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site