RE: [PATCH 1/2] ia64: ptrace - find memory sharers on children list

Luck, Tony
2005-10-27T18:03:46Z

>The ptrace caller (presumably a debugger) specifies the pid of
>its target and an address to peek or poke. But the debugger could be
>attached to several tasks.

Perhaps I'm being overly dense here (I haven't ever tried to
debug a multi-threaded application) ... but how can this situation
happen? Since ptrace takes a "pid" argument, I'd expect that any
activities performed by the kernel in response to that ptrace call
would be restricted to just the process that was mentioned. Searching
off through other processes to see if any of them have the data
just sounds wrong. Why can't the debugger keep track of which
process is which and give the right "pid" to the ptrace call?

-Tony