[U-Boot-Users] debug u-boot using bdi2000

[Ben Warren]

On Fri, 2006-10-13 at 13:38 -0500, Timur Tabi wrote:

> Ben Warren wrote:
> 
> > I don't know how well supported your CPU is (I've never heard of it, but
> > that's not saying much)  Anyway, I've debugged ROM on a couple of
> > different MPC8349s, but not with 100% success.  I can single-step with
> > the BDI, and can single-step assembly code, but not C code using gdb.
> 
> I don't know about PowerPC processors, but on x86, single-stepping assembly code is completely different from single-stepping C code.  With assembly, the debugger typically enables instruction interrupts, where an interrupt is generated after each instruction is executed.  This does not require modifying memory.
> 
> With C code, a single line of C code is usually multiple assembly instructions, so the debugger (gdb in this case) places a breakpoint at the appropriate spot.
> 

That's some good insight, and would certainly explain my problem.
Thanks!

Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20061013/d6074d06/attachment.htm