On Tue Aug 21 11:27:07 2007, [EMAIL PROTECTED] wrote:
>
> > Hi Balbir,
> >
> > That was what I wanted to do at first, but there was some concern over
> > whether it would affect any of the intervening function calls. If there's
> > no particular reason why the tsk->exit_code assignment is placed
Jonathan Lim wrote:
> On Mon Aug 20 20:44:13 2007, [EMAIL PROTECTED] wrote:
>> Jonathan Lim wrote:
>>> taskstats.ac_exitcode is assigned to task_struct.exit_code in
>>> bacct_add_tsk() through the following kernel function calls:
>>>
>>> do_exit()
>>> taskstats_exit_send()
>>> fill_pid
On Mon Aug 20 20:44:13 2007, [EMAIL PROTECTED] wrote:
>
> Jonathan Lim wrote:
> > taskstats.ac_exitcode is assigned to task_struct.exit_code in
> > bacct_add_tsk() through the following kernel function calls:
> >
> > do_exit()
> > taskstats_exit_send()
> > fill_pid()
> > bacc
Jonathan Lim wrote:
> taskstats.ac_exitcode is assigned to task_struct.exit_code in bacct_add_tsk()
> through the following kernel function calls:
>
> do_exit()
> taskstats_exit_send()
> fill_pid()
> bacct_add_tsk()
>
> The problem is that in do_exit(), task_struct.exit_code
4 matches
Mail list logo