lkcd
[Top] [All Lists]

Re: kl_parent_pid()

To: Steve James <saj@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: kl_parent_pid()
From: Tom Morano <tjm@xxxxxxx>
Date: Tue, 09 Jan 2001 16:35:40 -0800
Cc: lkcd@xxxxxxxxxxx, Tom Morano <tjm@xxxxxxx>
References: <200101092340.QAA19200@riscokid.phx.mcd.mot.com>
Sender: owner-lkcd@xxxxxxxxxxx
Steve James wrote:
> 
> Greetings!
> 
> This is my first mail to the list.  I'm porting the LKCD+lcrash
> as of 20 Dec 2000 to Linux 2.2.17 on the PowerPC.  So far,
> I am very impressed!
> 
> However, in the interest of better parent/child relationships,
> shouldn't the line:
> 
>         ppid = (uint64_t)KL_UINT(tsp, "task_struct", "pid");
> 
> in libklib/kl_task.c:kl_parent_pid()
> 
> rather read:
> 
>         ppid = (uint64_t)KL_UINT(tpp, "task_struct", "pid");

Hi Steve,

You are absolutely correct. Thanks! 

And thanks for doing work on a PowerPC port. From an lcrash point of
view, you can do a lot of work without actually having LKCD kernel 
functionality in place. As long as you have a "namelist" file you 
can start up lcrash on a live system. You need to make sure that
you run the configure script in lkcdutils with the --topdir flag
set to your kernel source tree (if it's not /usr/src/linux). You will 
then be able to do a 'make namelist' from within the libklib directory. 
Use the resulting namelist in the following manner:

# lcrash /boot/System.map /dev/mem namelist

You will then be able to work on the architecture specific stuff like
stack traces for running tasks. Or, you may already be beyond this point.

Thanks again,

Tom

Take care,

Tom

<Prev in Thread] Current Thread [Next in Thread>