<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>how about if crash utility supports breakpoints/watchpoints specifically hw level.</span></div><div><span>of course need a kernel module to modify kernel memory as you suggested.</span></div><div><br><span></span></div><div><span>was there any specific reason, you did not support this, thinking already kgdb and kdb types of utility available ?</span></div><div><span>If we support breakpoint./watchpoints in crash, will the crash be able to offer much better than any other kernel debug tools ?</span></div><div><br></div><div>what do you think? <br></div><div><br><span></span></div><div><span>Regards,</span></div><div><span>Oza.</span></div><div><br></div> <div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"> <div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight: bold;">From:</span></b> Dave Anderson <anderson@redhat.com><br> <b><span style="font-weight: bold;">To:</span></b> paawan oza <paawan1982@yahoo.com> <br><b><span style="font-weight: bold;">Cc:</span></b> "Discussion list for crash utility usage, maintenance and development" <crash-utility@redhat.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, 7 August 2012 6:58 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Crash-utility] using crash for ARM<br> </font> </div> <br><br><br>----- Original Message -----<br>> <br>> <br>> Hi Dave,<br>> <br>> Will I be able to set breakpoints and watch points in kernel space ?<br><br>Definitely not. Keep in mind that the crash utility is a simple<br>user-space program that happens to read kernel memory. It is not<br>a kernel debugger. Setting breakpoints/watch points requires the <br>capability of modifying kernel memory, setting up kernel handlers<br>to respond to the breakpoint interrupts, etc.<br><br>> Do you accept the changes/contribution to crash ?<br><br>Sure -- if you check the archives, you can see that posting patches<br>is one of the primary purposes for this mailing list.<br><br>Dave<br> <br>> Regards,<br>> Oza.<br>> <br>> <br>> <br>> <br>> <br>> From: Dave Anderson <<a ymailto="mailto:anderson@redhat.com" href="mailto:anderson@redhat.com">anderson@redhat.com</a>><br>> To: paawan oza <<a ymailto="mailto:paawan1982@yahoo.com" href="mailto:paawan1982@yahoo.com">paawan1982@yahoo.com</a>>; "Discussion list for crash<br>> utility usage, maintenance and development"<br>> <<a ymailto="mailto:crash-utility@redhat.com" href="mailto:crash-utility@redhat.com">crash-utility@redhat.com</a>><br>> Sent: Monday, 6 August 2012 8:58 PM<br>> Subject: Re: [Crash-utility] using crash for ARM<br>> <br>> <br>> <br>> ----- Original Message -----<br>> > <br>> > <br>> > <br>> > Hi,<br>> > <br>> > <br>> > I would like to use crash utility on ARM.<br>> > what I understand is there might be two ways to go about it.<br>> > <br>> > 1) cross compile whole crash for arm itself, which doesnt seem to<br>> > be<br>> > good option because on arm target we will need lots of depedent<br>> > packages.<br>> > <br>> > 2) run crash on x86 and have gdbserver/remoter server compiled on<br>> > target. and have serial connection and so on..<br>> > <br>> > please suggest instructions or any pointers regarding the same.<br>> > <br>> > Regards,<br>> > Oza.<br>> <br>> If you are talking about running crash on a live ARM system, then<br>> option #1 is the only possibility. Option #2 does not exist for<br>> the crash utility; live system access requires either /dev/mem,<br>> /proc/kcore, or the /dev/crash misc driver.<br>> <br>> Dave<br>> <br>> <br>> <br>> <br><br><br> </div> </div> </div></body></html>