From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [RFA] NEWS entry for recent gdbserver additions
Date: Tue, 30 Jun 2009 21:36:00 -0000 [thread overview]
Message-ID: <20090630213618.8643D846CA@localhost> (raw)
Hi.
Forgot NEWS entries for these.
Ok to check in?
2009-06-30 Doug Evans <dje@google.com>
* NEWS: Mention biarch amd64-linux gdbserver and hardware watchpoint
support for i386-linux, amd64-linux, and i386-win32 builds of
gdbserver.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.314
diff -u -p -r1.314 NEWS
--- NEWS 28 Jun 2009 00:20:21 -0000 1.314
+++ NEWS 30 Jun 2009 21:17:28 -0000
@@ -144,6 +144,13 @@ GDB will now correctly handle all of:
- Support for the sparc64-linux-gnu target is now included in
gdbserver.
+ - The amd64-linux build of gdbserver now supports debugging both
+ 32-bit and 64-bit programs.
+
+ - The i386-linux, amd64-linux, and i386-win32 builds of gdbserver
+ now support hardware watchpoints, and will use them automatically
+ as appropriate.
+
* Python scripting
GDB now has support for scripting using Python. Whether this is
next reply other threads:[~2009-06-30 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 21:36 Doug Evans [this message]
2009-07-01 3:03 ` Eli Zaretskii
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=20090630213618.8643D846CA@localhost \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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