From: David Frascone <dave@frascone.com>
To: Balaji Purushothaman <balajikp2000@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: remote stubs - Gdb for PowerPC
Date: Tue, 14 Sep 2004 16:15:00 -0000 [thread overview]
Message-ID: <20040914111536.61011d76.dave@frascone.com> (raw)
In-Reply-To: <20040914145554.61602.qmail@web53306.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
I've been looking for one for a while. The linux kernel has one . . and there is code in gdbserver for ppc, but no stub.
If you find one, please let me know . . . or if anyone is kind enough to port the gdbserver code to a gdbstub . . . My ppc assembly isn't good enough to try.
-Dave
On Tue, 14 Sep 2004 07:55:54 -0700 (PDT)
Balaji Purushothaman <balajikp2000@yahoo.com> wrote:
> Hi all,
>
> Does anyone has remote Stubs (GDB) for debugging the
> PowerPC target.
>
> Basically i need to debug the target through the
> serial port from the SUN host machine. In the host
> machine, i have a GDB debugger running.When the
> debugger issues any commands, target(stubs) should
> understand the GDB commands and respond properly.
> Stubs along with the OS will be running in the target.
> Basic functionality of GDB Stubs is Exception handling
> ,Debugging support and understand the GDB standard
> protocol.
>
> Thanks in Advance
>
> Regards,
> Balaji
>
>
>
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
>
--
David Frascone
Russian Express Card motto: Don't leave home!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-14 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 14:55 Balaji Purushothaman
2004-09-14 16:15 ` David Frascone [this message]
2004-09-14 17:55 Michael D. Crawford
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=20040914111536.61011d76.dave@frascone.com \
--to=dave@frascone.com \
--cc=balajikp2000@yahoo.com \
--cc=gdb@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).