Messages in this thread | | | Subject | Re: [RFC] [PATCH 4/7] Uprobes Implementation | From | Peter Zijlstra <> | Date | Fri, 15 Jan 2010 11:33:27 +0100 |
| |
On Fri, 2010-01-15 at 15:56 +0530, Srikar Dronamraju wrote: > Hi Peter, > > Or there could be two threads that could be racing to > insert/delete a breakpoint. These synchronization issues are all handled > by the Uprobes layer.
Shouldn't be hard to put that in the ubp layer, right?
> Uprobes layer would need to be notified of process life-time events > like fork/clone/exec/exit.
No so much the process lifetimes as the vma life times are interesting, placing a hook in the vm code to track that isn't too hard,
> It also needs to know > - when a breakpoint is hit > - stop and resume a thread.
A simple hook in the trap code is done quickly enough, and no reason to stop the thread, its not going anywhere when it traps.
| |