From: diekema@bucks.si.com (diekema_jon)
To: bgat@usa.net
Cc: all@cideas.com, linuxppc-embedded@lists.linuxppc.org,
gdb@sourceware.cygnus.com
Subject: Looking for the PPC gdb debug stubs
Date: Fri, 4 Feb 2000 12:58:07 -0500 (EST) [thread overview]
Message-ID: <m12Gmzf-001SweC@bucks> (raw)
To: Bill Gatliff
bgat@usa.net
Subj: Looking for the PPC gdb debug stubs
In your 9/99 article in Embedded Systems Programming, you hint
about the Power PC gdb debug stubs being in progress. Can you
provide with any details like:
- Is the effort complete?
- If so, where can I find the PPC gdb debug stubs?
- Who are the people involved with the activity,
and how can I get in touch with them?
Our initial hardware target is the EST SBC8260 board. The MPC8260
supports a COP/JTAG port. I wondered if gdb has or is the progess
of supporting the MPC8260 Macraigor Wiggler? From the gdb version
4.18 source code, it appears that gdb supports the MPC860
Macraigor Wiggler.
Note: The MPC860 and MPC8260 Wigglers are very different animals.
Reference:
http://www.embedded.com/1999/9909/9909feat2.htm
I have posted my attempt at a portable debugging stub on ESPs Web
site, at ftp://ftp.mfi.com/pub/espmag/1999/gdb. This source code
has been compiled and tested for the Hitachi SH-2, and ports are
underway for the Hitachi H8, Power PC, and other processors.
Who is Bill Gatliff?
Bill Gatliff is a freelance embedded developer and senior design
engineer with Komatsu Mining Systems, Inc. in Peoria, IL, and is a
semi-regular presenter at the Embedded Systems Conferences. He can
be reached at bgat@usa.net.
GDB: The GNU Debugger
http://sourceware.cygnus.com/gdb/
GDB Mailing Lists
http://sourceware.cygnus.com/gdb/lists.html
gdb@sourceware.cygnus.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-02-04 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 17:58 diekema_jon [this message]
2000-02-05 0:57 ` Looking for the PPC gdb debug stubs Dan Malek
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=m12Gmzf-001SweC@bucks \
--to=diekema@bucks.si.com \
--cc=all@cideas.com \
--cc=bgat@usa.net \
--cc=gdb@sourceware.cygnus.com \
--cc=linuxppc-embedded@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).