From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [RFC, docs RFA] gdbserver and gdb.threads/attach-into-signal.exp.
Date: Wed, 07 Mar 2012 18:25:00 -0000 [thread overview]
Message-ID: <4F57A80E.1040809@redhat.com> (raw)
In-Reply-To: <83fwdla6w3.fsf@gnu.org>
Hi Eli,
On 03/06/2012 07:03 PM, Eli Zaretskii wrote:
> The documentation is fine. I think this warrants a NEWS entry (all
> new packets do).
Thanks. How's this?
2012-03-07 Pedro Alves <palves@redhat.com>
* NEWS: Add subtitle for new z0/z1 conditional breakpoint
extensions. Mention QProgramSignals.
---
gdb/NEWS | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 3051c74..1475f96 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -90,11 +90,18 @@ show breakpoint condition-evaluation
* New remote packets
+z0/z1 conditional breakpoints extension
+
The z0/z1 breakpoint insertion packets have been extended to carry
a list of conditional expressions over to the remote stub depending on the
condition evaluation mode. The use of this extension can be controlled
via the "set remote conditional-breakpoints-packet" command.
+QProgramSignals:
+
+ Signals the remote stub may pass to the debugged program, without
+ GDB involvement.
+
*** Changes in GDB 7.4
* GDB now handles ambiguous linespecs more consistently; the existing
next prev parent reply other threads:[~2012-03-07 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 19:29 Pedro Alves
2012-02-23 4:07 ` Yao Qi
2012-02-24 21:29 ` Pedro Alves
2012-02-25 12:19 ` Yao Qi
2012-03-06 18:26 ` Pedro Alves
2012-03-06 19:04 ` Eli Zaretskii
2012-03-07 18:25 ` Pedro Alves [this message]
2012-03-07 18:53 ` Eli Zaretskii
2012-03-07 19:20 ` NEWS: Add subtitle for new z0/z1 conditional breakpoint extensions Pedro Alves
2012-03-07 19:28 ` [PATCH] [RFC, docs RFA] gdbserver and gdb.threads/attach-into-signal.exp Pedro Alves
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=4F57A80E.1040809@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--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