Hi,
After applying below patches
kdb-v4.4-2.6.24-common-2.bz2
kdb-v4.3-2.4.20-xscale-1.bz2
and after bit of struggle I was able to enter the kdb prompt setting
kdb=early flag on a OMAP3430 based target.
Now I am trying other entry methods
a) Automatic entry when exception, divide by zero and NULL pointer
derefernce happens
For NULL pointer derefernce, I am calling the API kdb inside die() in
file arch/arm/kernel/traps.c
But kdb behaviour here is not the same as in case of kdb=early entry;
For ex: id command does not work ..etc
Please let me know is this a correct way to proceed?
b) Through key press <esc> KDB.
I am not using the serial console driver; instead I am directly
writing/reading from the low-level uart driver.
In this case how will the KDB come to know about the keypress.
As a workaround, I have an executable which will call a driver ioctl and
inside the driver ioctl I am calling the API kdb()
Here also I am facing the same behaviour
[Note if I use the macro KDB_ENTER instead kdb() I get a bad memory
address error in kdb_getarea]
Any clarifications as to whats missing/wrong will be very helpful
Regards
Basavaraj
On Thu, Jun 4, 2009 at 3:08 PM, Basavaraj Dengi <[email protected]>wrote:
> Hi
>
> The kdb patch for xscal processor is for 2.4.20 kernel.
> Is there any latest patch available?
> I dont see any 2.6.x patches for ARMv7 on the website
> ftp://oss.sgi.com/projects/kdb/download
>
> and also on google.
>
> I will be very thankful for any links /suggestions
>
> Regards
> Basavaraj
>
_______________________________________________
kdb mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/kdb
