Re: [microblaze-uclinux] kernel debugging

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Falk,

Brettschneider Falk wrote:

> I followed the instructions on http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux/Documentation/debugging_kernel.html and was able to debug into the kernel by setting breakpoints, interrupting the process with Ctrl+C and retrieving backtraces with the gdb command 'bt'. So far so cool.
>
> But were you able to step through the code? Executing gdb command 'step' seems to continue but then it hangs and Ctrl+C doesn't react anymore.

I haven't tried this for a while - to be honest I find printk logging 
much more effective than single stepping.  If you do a kind of binary 
search on the failure or issue you are seeking, you can converge 
pseudo-logarithmically, rather than spending hours singlestepping.

Also, single stepping when theer are interrupts and exceptions going on 
can be problematic.  XMD's hardware debugging is not quite as 
software-transparent as it seems.

> Furthermore, I started microblaze-uclinux-gdb without command-line argument -nw to work in graphical user interface mode. In this case I wasn't able to load and run the program. Those ones who succeeded, can you help me with a short How-To, please?

This one is easy

<start xmd, connect to the MDM>

$ mb-gdb -nw linux-2.6.x/linux
$ target remote localhost:1234

break start_kernel
con

...


Cheers,

John

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/