From: William Gatliff <gatliff@haulpak.com>
To: all@cideas.com, linuxppc-embedded@lists.linuxppc.org,
gdb@sourceware.cygnus.com
Subject: Re: [Looking for the PPC gdb debug stubs]
Date: Mon, 07 Feb 2000 09:31:56 -0600 [thread overview]
Message-ID: <389EE56C.47EEBDE@haulpak.com> (raw)
In-Reply-To: Pine.SGI.3.95.1000207100549.24603E-100000@world.std.com
Aleksey:
> > > - If so, where can I find the PPC gdb debug stubs?
>
> You can try the thing I put togehter at
> http://www.std.com/qqi/labslave/rproxy.html
>
> Among other things it provides an application bridge between wiggler (BDM
> debugger from macraigor) and gdb remote protocol.
Yes, that's an even better solution than a stub, on targets and platforms that can
support it, becuase it does in hardware what the stub does in software.
b.g.
--
William A. Gatliff
Senior Design Engineer
Komatsu Mining Systems
To teach is to learn.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-02-07 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-07 2:32 [Looking for the PPC gdb debug stubs] William A.Gatliff
2000-02-07 15:08 ` Quality Quorum
2000-02-07 15:31 ` William Gatliff [this message]
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=389EE56C.47EEBDE@haulpak.com \
--to=gatliff@haulpak.com \
--cc=all@cideas.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.