From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: gdbserver implementation
Date: Thu, 10 Apr 2003 20:02:00 -0000 [thread overview]
Message-ID: <035601c2ff9c$2bccd360$0202040a@catdog> (raw)
In-Reply-To: <034201c2ff9a$731c5bc0$0202040a@catdog>
> I've never used gdbserver before. How does its feature set compare to
this?
> We wanted to see how well gdbserver worked for us and were considering
> migrating to get away from the pdebug protocol issues.
I should say that one of the reasons for this is that we now have an IDE
with it's own remote agent that does a great deal of the fancy stuff so it's
not required at the pdebug/gdbserver level. The remote agent sets
everything up and then just spawns pdebug to talk to gdb. One of the big
pains in our pdebug protocol is the extents that it goes to in ensuring
reliable communication. It's a good feature but it's also where things
occasionally fall down due to the complexity. If the IDE's agent is
ensuring reliable communication, then none of that code is required and
gdbserver might be just the thing.
cheers,
Kris
prev parent reply other threads:[~2003-04-10 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 19:17 Kris Warkentin
2003-04-10 19:26 ` Daniel Jacobowitz
2003-04-10 19:50 ` Kris Warkentin
2003-04-10 20:02 ` Kris Warkentin [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='035601c2ff9c$2bccd360$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=drow@mvista.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