From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Using the abatron to debug an image in flash
Date: 07 Aug 2003 13:45:08 +0200 [thread overview]
Message-ID: <87vft9u1x7.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: <9901EE1E8F8BD3119109009027A1B5F596AE40@DIGINET2>
Hi Mark,
[...]
> As you can see the code appears to jump around aimlessly, though the
> program still appears to run ok. Just to finish off I am able to
> configure the ram such that I can debug the application in ram up to
> the point where relocation occurs so I am fairly confident in my
> SDRAM setup.
If the "random jumping" is your only problem, then you don't really
have a problem. The behaviour is due to the fact the gcc has
reordered the assembler instructions to better fit the PowerPC
architecture which means that the assembler instruction sequence
_does not_ correspond 1:1 to the source lines.
If this is the problem in your case, you can try disabling all code
optimizations (-O0) for your debugging sessions. If I am not
mistaken, this should enforce a 1:1 correspondence from source to
assembler instructions.
Cheers
Detlev
--
PUBLIC NOTICE AS REQUIRED BY LAW: Any Use of This Product, in Any Manner
Whatsoever, Will Increase the Amount of Disorder in the Universe. Although No
Liability Is Implied Herein, the Consumer Is Warned That This Process Will
Ultimately Lead to the Heat Death of the Universe.
next prev parent reply other threads:[~2003-08-07 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 10:39 [U-Boot-Users] Using the abatron to debug an image in flash Mark Doherty
2003-08-07 11:45 ` Detlev Zundel [this message]
2003-08-07 12:30 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 15:00 Mark Doherty
2003-08-07 15:22 ` Wolfgang Denk
2003-08-07 15:23 ` Detlev Zundel
2003-08-07 15:41 Mark Doherty
2003-08-07 16:32 ` Wolfgang Denk
2003-08-08 8:33 Mark Doherty
2003-08-08 12:06 Mark Doherty
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=87vft9u1x7.fsf@deepthought.outer.space.org \
--to=dzu@denx.de \
--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