debugging on ppc with xmon

[Segher Boessenkool]

> 	When I rebooted this kernel, it oopsed in xmon right after prom_init,
> with a data SLB access (which in this case is most likely to be a
> wrong memory
> reference or null pointer reference).

Null pointer references do not fail here :-(  -- so it is some
other "wrong" access.

> 	How can I obtain a objdump output with source line corelation to the
> assembly code?

objdump -drS vmlinux

It will only show the C source files though, and/or only when
you have kernel debug info enabled.  Also, it is pretty useless
at any decent compiler optimization level IMHO.

> 	Any pointers or directions as to how to debug this would be helpful,
> as I am starting off with ppc debugging with this as the first.

I normally just insert a boatload of printk()'s, see what interval
it fails in, and refine.  Repeat until done.

Or set a lot of breakpoints in your debugger -- basically the same
thing,
but less convenient.


Segher


** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/