From: Wolfgang Denk <wd@denx.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: BDM for Linux Kernel Debugging - MMU Support available
Date: Thu, 13 Jul 2000 16:33:09 +0200 [thread overview]
Message-ID: <200007131433.QAA23929@denx.local.net> (raw)
Hi everybody,
so far, a BDM debugger was of no much use for Linux kernel debugging:
once the MMU is turned on (pretty early during kernel initialization)
the BDM debugger is confronted with virtual addresses, and so far
they just barfed.
This has changed:
* Frank Przybylski has added software-tablewalk code to his GDB
extensions for the MPCBDM "Do-it-yourself" debugger, see
http://www.vas-gmbh.de/software/mpcbdm/
* Abatron has implemented MMU support in recent firmware versions for
their BDI box (see http://www.abatron.ch/BDI/bdimain.html); AFAIK
they are the first tool provider that offers commercial MMU sup-
port, and what's even more interesting: they provide it especially
with Linux in their mind. [Right now available for MPC8xx CPUs,
with PPC6xx/7XX (including MPC82xx) in the works.]
So we now have both a "free" and a "professional" solution for BDM
based Linux kernel debugging, both interfacing with GDB (or DDD if
you like) and allowing to debug kernel code (single stepping, break-
points, etc.) and/or inspect kernel data... From what I've seen so
far, both solutions provide the same features, and work with about
the same speed - and with the same results.
Hope this helps,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The software required `Windows 95 or better', so I installed Linux.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-13 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 14:33 Wolfgang Denk [this message]
2000-07-13 16:45 ` BDM for Linux Kernel Debugging - MMU Support available Franz Sirl
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=200007131433.QAA23929@denx.local.net \
--to=wd@denx.de \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).