public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] debug u-boot using bdi2000
Date: Fri, 13 Oct 2006 13:38:50 -0500	[thread overview]
Message-ID: <452FDD3A.1050004@freescale.com> (raw)
In-Reply-To: <1160764494.27646.91.camel@saruman.qstreams.net>

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.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2006-10-13 18:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 17:41 [U-Boot-Users] debug u-boot using bdi2000 Reeve Yang
2006-10-13 18:05 ` Ben Warren
2006-10-13 18:12   ` Reeve Yang
2006-10-13 18:23     ` Reeve Yang
2006-10-13 18:44       ` Ben Warren
2006-10-13 18:34     ` Ben Warren
2006-10-13 18:38       ` Timur Tabi [this message]
2006-10-13 18:48         ` Ben Warren
2006-10-13 18:52           ` Brent Cook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=452FDD3A.1050004@freescale.com \
    --to=timur@freescale.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox