From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: Nick Bull <nicholaspbull@gmail.com>,
gdb-patches <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH v8] Events when inferior is modified
Date: Mon, 15 Dec 2014 08:33:00 -0000 [thread overview]
Message-ID: <87r3w1tiqy.fsf@codesourcery.com> (raw)
In-Reply-To: <21630.4311.741887.195958@ruffy2.mtv.corp.google.com> (Doug Evans's message of "Tue, 2 Dec 2014 11:19:51 -0800")
Doug Evans <dje@google.com> writes:
> diff --git a/gdb/NEWS b/gdb/NEWS
> index d38266f..7262502 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -1,6 +1,16 @@
> What has changed in GDB?
> (Organized release by release)
>
> +* Python Scripting
> +
> + New events which are triggered when GDB modifies the state of the
> + inferior.
> +
> + ** gdb.events.inferior_call_pre: Function call is about to be made.
> + ** gdb.events.inferior_call_post: Function call has just been made.
> + ** gdb.events.memory_changed: A memory location has been altered.
> + ** gdb.events.register_changed: A register has been altered.
> +
> *** Changes since GDB 7.8
These entries should go to "Changes since GDB 7.8" section. This patch
moves them there.
--
Yao (齐尧)
From: Yao Qi <yao@codesourcery.com>
Date: Mon, 15 Dec 2014 16:29:21 +0800
Subject: [PATCH] Move NEWS entries to the right section
gdb:
2014-12-15 Yao Qi <yao@codesourcery.com>
* NEWS: Move some entries to "Changes since GDB 7.8" section.
diff --git a/gdb/NEWS b/gdb/NEWS
index 168e810..75a05c3 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,16 +1,6 @@
What has changed in GDB?
(Organized release by release)
-* Python Scripting
-
- New events which are triggered when GDB modifies the state of the
- inferior.
-
- ** gdb.events.inferior_call_pre: Function call is about to be made.
- ** gdb.events.inferior_call_post: Function call has just been made.
- ** gdb.events.memory_changed: A memory location has been altered.
- ** gdb.events.register_changed: A register has been altered.
-
*** Changes since GDB 7.8
* GDB now supports hardware watchpoints on x86 GNU Hurd.
@@ -30,6 +20,14 @@
** You can now add attributes to gdb.Objfile and gdb.Progspace objects.
** New function gdb.lookup_objfile.
+ New events which are triggered when GDB modifies the state of the
+ inferior.
+
+ ** gdb.events.inferior_call_pre: Function call is about to be made.
+ ** gdb.events.inferior_call_post: Function call has just been made.
+ ** gdb.events.memory_changed: A memory location has been altered.
+ ** gdb.events.register_changed: A register has been altered.
+
* New Python-based convenience functions:
** $_caller_is(name [, number_of_frames])
next prev parent reply other threads:[~2014-12-15 8:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 17:32 [PATCH v6] " Nick Bull
2014-09-24 14:05 ` Robert O'Callahan
2014-09-25 10:14 ` Phil Muldoon
2014-10-01 9:50 ` Nick Bull
2014-10-01 17:52 ` Pedro Alves
2014-10-17 16:26 ` [PATCH v7] " Nick Bull
2014-10-17 19:49 ` Doug Evans
2014-10-17 20:00 ` Doug Evans
2014-10-22 12:40 ` [PATCH v8] " Nick Bull
2014-11-17 18:13 ` Nick Bull
2014-11-17 21:25 ` Doug Evans
2014-11-18 16:37 ` Nick Bull
2014-11-20 0:21 ` Doug Evans
2014-11-20 10:36 ` Nick Bull
2014-12-02 19:20 ` Doug Evans
2014-12-04 10:45 ` Nick Bull
2014-12-15 8:33 ` Yao Qi [this message]
2014-10-24 15:14 ` [PATCH v7] " Pedro Alves
2014-11-06 18:19 ` Doug Evans
2014-11-07 12:21 ` Pedro Alves
2014-11-07 17:04 ` Doug Evans
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=87r3w1tiqy.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=nicholaspbull@gmail.com \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).