From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
gdb-patches@sourceware.org
Subject: Re: [RFC] Add new commands to windows native code.
Date: Fri, 09 Aug 2013 15:03:00 -0000 [thread overview]
Message-ID: <5204FCE6.60203@redhat.com> (raw)
In-Reply-To: <83d2pnrmbn.fsf@gnu.org>
I'd be good to keep GDBserver in the loop too. We're
trying to bridge the gap between GDB and GDBserver afterall,
and new features in the native target that don't end up
in GDBserver now just means more work later on.
IOW, it'd be very good to keep the RSP and GDBserver in
mind when designing the implementation for such a feature
(whatever it ends up looking like).
--
Pedro Alves
next prev parent reply other threads:[~2013-08-09 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"001f01ce9413$72450b20$56cf2160$@muller"@ics-cnrs.unistra.fr>
2013-08-09 14:06 ` Eli Zaretskii
2013-08-09 15:03 ` Pedro Alves [this message]
2013-08-19 14:39 ` Pierre Muller
[not found] ` <"000001ce9ce9$d4669a10$7d33ce30$@muller"@ics-cnrs.unistra.fr>
2013-08-19 15:55 ` Eli Zaretskii
2013-08-08 8:44 Pierre Muller
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=5204FCE6.60203@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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