Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: jauming@yahoo.com
Cc: gdb@cygnus.com
Subject: Re: newbie question
Date: Mon, 19 Apr 1999 12:56:00 -0000	[thread overview]
Message-ID: <199904191956.MAA18773@andros.cygnus.com> (raw)
In-Reply-To: <19990419081407.2019.rocketmail@send102.yahoomail.com>

   Date: Mon, 19 Apr 1999 01:14:07 -0700 (PDT)
   From: JauMing Tseng <jauming@yahoo.com>

   1)is [gdb stub] needed by [pmon of mips]?

No.

   2)which protocol is better?
     a)pmon mips remote debugging protocol
     b)native gdb remote debugging protocol

GDB's native protocol, of course. :-) But seriously, the mips protocol
is less efficient, requiring more line traffic, and it's binary, which
makes debugging harder.  It's also a little more complicated, which
likely means more target-side code to write.

All in all, I would recommend the use of GDB's own protocol, unless
you have some other reason to use PMON in your target.

								Stan



      parent reply	other threads:[~1999-04-19 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-19  1:12 JauMing Tseng
1999-04-19  2:24 ` JauMing Tseng
1999-04-19 12:56 ` Stan Shebs [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=199904191956.MAA18773@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=gdb@cygnus.com \
    --cc=jauming@yahoo.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