From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>,
"'Pedro Alves'" <pedro@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: PING: Mingw64 gdbserver support NEWS entry
Date: Thu, 29 Apr 2010 21:36:00 -0000 [thread overview]
Message-ID: <001501cae7e4$092e9d10$1b8bd730$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <002701cae020$4c88a7c0$e599f740$@muller@ics-cnrs.unistra.fr>
> You suggested a NEWS entry,
> I hesitated to put (mingw64)...
>
> Comments?
Nobody reacted to this part of
one of my emails.
At one point, someone said, that a
new gdbserver port should be reported in NEWS.
Eli, maybe you have a better idea for
the wording?
> Pierre
>
> Index: NEWS
> ===================================================================
> RCS file: /cvs/src/src/gdb/NEWS,v
> retrieving revision 1.373
> diff -u -r1.373 NEWS
> --- NEWS 19 Apr 2010 00:48:43 -0000 1.373
> +++ NEWS 20 Apr 2010 00:25:02 -0000
> @@ -27,6 +27,8 @@
> - GDBserver now support tracepoints. The feature is currently
> supported by the i386-linux and amd64-linux builds.
>
> + - GDBserver now supports x86_64 Windows 64-bit debugging.
> +
> * GDB now sends xmlRegisters= in qSupported packet to indicate that
> it understands register description.
next prev parent reply other threads:[~2010-04-29 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 22:51 [RFA] [0/4] Mingw64 gdbserver support Pierre Muller
2010-04-19 23:32 ` Pedro Alves
2010-04-20 0:27 ` Pierre Muller
2010-04-29 21:36 ` Pierre Muller [this message]
[not found] ` <002701cae020$4c88a7c0$e599f740$%muller@ics-cnrs.unistra.fr>
[not found] ` <001501cae7e4$092e9d10$1b8bd730$%muller@ics-cnrs.unistra.fr>
2010-04-30 6:24 ` PING: Mingw64 gdbserver support NEWS entry Eli Zaretskii
2010-04-30 7:05 ` 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='001501cae7e4$092e9d10$1b8bd730$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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