<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY>
On Fri, 2006-10-13 at 13:38 -0500, Timur Tabi wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Ben Warren wrote:</FONT>
<FONT COLOR="#000000">> I don't know how well supported your CPU is (I've never heard of it, but</FONT>
<FONT COLOR="#000000">> that's not saying much) Anyway, I've debugged ROM on a couple of</FONT>
<FONT COLOR="#000000">> different MPC8349s, but not with 100% success. I can single-step with</FONT>
<FONT COLOR="#000000">> the BDI, and can single-step assembly code, but not C code using gdb.</FONT>
<FONT COLOR="#000000">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.</FONT>
<FONT COLOR="#000000">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.</FONT>
</PRE>
</BLOCKQUOTE>
That's some good insight, and would certainly explain my problem. Thanks!<BR>
<BR>
Ben
</BODY>
</HTML>