From: Richard Danter <richard.danter@windriver.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 750/107 CHRP question
Date: Fri, 01 Aug 2003 10:02:46 +0100 [thread overview]
Message-ID: <3F2A2CB6.4030104@windriver.com> (raw)
In-Reply-To: 20030801082845.A38F6C602D@atlas.denx.de
Wolfgang Denk wrote:
> In message <3F2A21D5.2040204@windriver.com> you wrote:
>
>>There is a command in the vICE-II called "CF MMU LINUX" which turns on
>>MMU handling (doesn't have to be Linux running) and then you use the
>>MMUA command to set up the mapping (eg MMUA C0000000 0 F0000000) and hey
>>presto!
>
> Will this work just for code statically linked with the kernel, or
> also for dynamically loaded modules? How about accessing dynamic
> variables on the stack?
>
> My understanding is that more than just a static mapping is needed
> for full MMUP support.
You are correct. Only the kernel and drivers statically linked can be
easily debugged. It could be possible to debug modules but since the
addresses change every time you load them it would not be practical. You
would have to edit the symbol files (*.ab) each time.
For complete MMU handling the debugger would need to know where to find
the mapping tables and remap it's symbol info. None of our debuggers can
do that yet.
Rich
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-08-01 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030801082845.A38F6C602D@atlas.denx.de>
2003-08-01 9:02 ` Richard Danter [this message]
2003-08-01 12:17 ` 750/107 CHRP question Wolfgang Denk
2003-08-01 12:24 ` Richard Danter
2003-07-31 16:54 Richard Danter
2003-07-31 21:07 ` Matt Porter
2003-07-31 21:41 ` Richard Danter
2003-07-31 22:48 ` Matt Porter
2003-07-31 23:32 ` Wolfgang Denk
2003-08-01 8:16 ` Richard Danter
2003-08-01 4:34 ` Sangmoon Kim
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=3F2A2CB6.4030104@windriver.com \
--to=richard.danter@windriver.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@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;
as well as URLs for NNTP newsgroup(s).