Just curious....

a.   What are the essential capabilities/features of kdump?   As far
as I know kdump is only a stacktrace, but systap tool can deliver
stack trace at many user-defined functions....and it has other
features to extract out the dynamic values of the variables....much
more powerful....

b.   Is the various memory snapshot tools provided by /proc fs and
/dev/*mem* not enough?   (/proc/vmstat, /proc/kcore (piped to xxd)),
/proc/iomem, /dev/mem (piped to xxd) etc)

On 4/28/08, Bernhard Walle <[EMAIL PROTECTED]> wrote:
> Hi,
>
>  * Mrunal Gawade [2008-04-25 14:30]:
>
> >
>  > I am trying to generate a dump for 2.6.18 Linux kernel to check bugs in my
>  > kernel code. For that I need to patch kernel with LKCD. But the latest LKCD
>  > patch available is for 2.6.10 and it seems it is not being updated
>  > frequently. I am not able to patch my kernel with 2.6.10 patch.
>  >
>  > Could anybody tell me is there any way to do this?
>
>
> The latest LKCD patch in CVS is 2.6.17. But you really should use kdump
>  for kernels later than 2.6.16 since it's mainline.
>
>
>         Bernhard
>
>
>
>
>  --
>  To unsubscribe from this list: send an email with
>  "unsubscribe kernelnewbies" to [EMAIL PROTECTED]
>  Please read the FAQ at http://kernelnewbies.org/FAQ
>
>


-- 
Regards,
Peter Teoh

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://kernelnewbies.org/FAQ

Reply via email to