From: Dave Anderson <anderson@redhat.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: "Discussion list for crash utility usage, maintenance and development" <crash-utility@redhat.com>
Sent: Tuesday, 7 August 2012 6:58 PM
Subject: Re: [Crash-utility] using crash for ARM
----- Original Message -----
>
>
> Hi Dave,
>
> Will I be able to set breakpoints and watch points in kernel space ?
Definitely not. Keep in mind that the crash utility is a simple
user-space program that happens to read kernel memory. It is not
a kernel debugger. Setting
breakpoints/watch points requires the
capability of modifying kernel memory, setting up kernel handlers
to respond to the breakpoint interrupts, etc.
> Do you accept the changes/contribution to crash ?
Sure -- if you check the archives, you can see that posting patches
is one of the primary purposes for this mailing list.
Dave
> Regards,
> Oza.
>
>
>
>
>
> From: Dave Anderson <
anderson@redhat.com>
> To: paawan oza <
paawan1982@yahoo.com>; "Discussion list for crash
> utility usage, maintenance and development"
> <
crash-utility@redhat.com>
> Sent: Monday, 6 August 2012 8:58
PM
> Subject: Re: [Crash-utility] using crash for ARM
>
>
>
> ----- Original Message -----
> >
> >
> >
> > Hi,
> >
> >
> > I would like to use crash utility on ARM.
> > what I understand is there might be two ways to go about it.
> >
> > 1) cross compile whole crash for arm itself, which doesnt seem to
> > be
> > good option because on arm target we will need lots of depedent
> > packages.
> >
> > 2) run crash on x86 and have gdbserver/remoter server compiled on
> > target. and have serial connection and so on..
> >
> > please suggest instructions or any pointers regarding the same.
> >
> > Regards,
> > Oza.
>
> If you are talking about running crash on a live ARM system, then
> option #1 is the only
possibility. Option #2 does not exist for
> the crash utility; live system access requires either /dev/mem,
> /proc/kcore, or the /dev/crash misc driver.
>
> Dave
>
>
>
>