On Tue, Feb 28, 2012 at 03:58, Vimal wrote:
> Hi Mulyadi,
>
> You were right. I found this code, which is called from
> ptrace_attach function:
>
> http://lxr.free-electrons.com/source/kernel/ptrace.c#L41
Phe :) Like I said i am getting rusty :) glad to help btw :D
--
regards,
Mulya
Hi Mulyadi,
You were right. I found this code, which is called from
ptrace_attach function:
http://lxr.free-electrons.com/source/kernel/ptrace.c#L41
Thanks :)
On 27 February 2012 08:45, Vimal wrote:
> Hi Mulyadi,
>
> On 26 February 2012 23:48, Mulyadi Santosa wrote:
>> I am bit rusty here,
Hi Mulyadi,
On 26 February 2012 23:48, Mulyadi Santosa wrote:
> I am bit rusty here, but AFAIK sigchld is thrown to the process who
> ptrace another process. CMIIW
>
sigchld's definition [1] says it's sent to the parent process when a
child terminates.
But I do agree that the notion of a parent
Hi Vimal...
On Mon, Feb 27, 2012 at 03:40, Vimal wrote:
> The documentation in sched.h:1313 says that "parent" refers to the
> parent task that would receive SIGCHLD (i.e., the one that issues
> wait4()). I followed the wait4() syscall to do_wait(), I still am not
> able to find where the task's
Hi,
I am looking through kernel 3.2's task_struct, which has two pointers
for parents: real_parent and parent
(http://lxr.free-electrons.com/source/include/linux/sched.h#L1313) I
would like to know why there are two pointers, and how these two
differ.
init_task's parent and real_parent are ini
