From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [RFC 00/12 V2] Visit varobj available children only in MI
Date: Fri, 14 Feb 2014 08:46:00 -0000 [thread overview]
Message-ID: <1392367471-13527-1-git-send-email-yao@codesourcery.com> (raw)
This is the V2 of this patch series, addressing Keith's review comments
to V1 (reviewed in Jan 2014). The general description of this series
can be found https://sourceware.org/ml/gdb-patches/2013-11/msg00739.html
Changes in V2 are:
- Include NEWS and doc.
- Fix typos, grammatical mistakes, and changelog entries.
- Update copyright year from "2013" to "2013-2014" for new files.
- Use -list-features to return "available-children-only" (#7).
- Update config/djgpp/fnchange.lst for new tests.
- Fix a missing cleanup (#2).
- Call varobj_delete_iter in free_variable (#3).
Regression tested on x86_64-linux.
*** BLURB HERE ***
Yao Qi (12):
Use 'struct varobj_item' to represent name and value pair
Generalize varobj iterator
Iterate over 'struct varobj_item' instead of PyObject
Remove #if HAVE_PYTHON
Rename varobj_pretty_printed_p to varobj_is_dynamic_p
Use varobj_is_dynamic_p more widely
MI option --available-children-only
Iterator varobj_items by their availability
Delete varobj's children on traceframe is changed.
Match dynamic="1" in the output of -var-list-children
Test case
NEWS and Doc on --available-children-only
gdb/Makefile.in | 17 +-
gdb/NEWS | 7 +
gdb/config/djgpp/fnchange.lst | 4 +
gdb/doc/gdb.texinfo | 62 +++-
gdb/mi/mi-cmd-var.c | 136 +++++++--
gdb/mi/mi-main.c | 1 +
gdb/python/py-varobj.c | 198 ++++++++++++
gdb/python/python-internal.h | 4 +
gdb/testsuite/gdb.trace/available-children-only.c | 69 ++++
gdb/testsuite/gdb.trace/available-children-only.cc | 45 +++
.../gdb.trace/mi-available-children-only-cxx.exp | 126 ++++++++
.../gdb.trace/mi-available-children-only.exp | 198 ++++++++++++
gdb/testsuite/lib/mi-support.exp | 17 +-
gdb/varobj-iter-avail.c | 162 ++++++++++
gdb/varobj-iter.h | 76 +++++
gdb/varobj.c | 327 ++++++++++----------
gdb/varobj.h | 15 +-
17 files changed, 1257 insertions(+), 207 deletions(-)
create mode 100644 gdb/python/py-varobj.c
create mode 100644 gdb/testsuite/gdb.trace/available-children-only.c
create mode 100644 gdb/testsuite/gdb.trace/available-children-only.cc
create mode 100644 gdb/testsuite/gdb.trace/mi-available-children-only-cxx.exp
create mode 100644 gdb/testsuite/gdb.trace/mi-available-children-only.exp
create mode 100644 gdb/varobj-iter-avail.c
create mode 100644 gdb/varobj-iter.h
--
1.7.7.6
next reply other threads:[~2014-02-14 8:46 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 8:46 Yao Qi [this message]
2014-02-14 8:46 ` [PATCH 09/12] Delete varobj's children on traceframe is changed Yao Qi
2014-04-24 20:45 ` Keith Seitz
2014-02-14 8:46 ` [PATCH 10/12] Match dynamic="1" in the output of -var-list-children Yao Qi
2014-04-24 20:50 ` Keith Seitz
2014-02-14 8:46 ` [PATCH 04/12] Remove #if HAVE_PYTHON Yao Qi
2014-04-23 19:25 ` Keith Seitz
2014-05-21 17:52 ` Tom Tromey
2014-02-14 8:46 ` [PATCH 06/12] Use varobj_is_dynamic_p more widely Yao Qi
2014-04-24 18:17 ` Keith Seitz
2014-05-21 18:04 ` Tom Tromey
2014-02-14 8:46 ` [PATCH 02/12] Generalize varobj iterator Yao Qi
2014-04-23 19:24 ` Keith Seitz
2014-05-21 17:51 ` Tom Tromey
2014-05-23 1:23 ` Yao Qi
2014-06-04 20:21 ` Tom Tromey
2014-06-05 5:36 ` Yao Qi
2014-06-05 18:21 ` Tom Tromey
2014-02-14 8:46 ` [PATCH 03/12] Iterate over 'struct varobj_item' instead of PyObject Yao Qi
2014-04-23 19:29 ` Keith Seitz
2014-05-21 18:01 ` Tom Tromey
2014-05-23 1:33 ` Yao Qi
2014-06-04 20:22 ` Tom Tromey
2014-02-14 8:46 ` [PATCH 12/12] NEWS and Doc on --available-children-only Yao Qi
2014-02-14 9:40 ` Eli Zaretskii
2014-02-17 9:46 ` Yao Qi
2014-02-17 15:04 ` Eli Zaretskii
2014-02-18 2:01 ` Yao Qi
2014-02-18 5:11 ` Eli Zaretskii
2014-02-18 7:14 ` Yao Qi
2014-02-18 15:07 ` Eli Zaretskii
2014-02-14 8:46 ` [PATCH 07/12] MI option --available-children-only Yao Qi
2014-04-24 20:02 ` Keith Seitz
2014-02-14 8:46 ` [PATCH 01/12] Use 'struct varobj_item' to represent name and value pair Yao Qi
2014-04-23 18:16 ` Keith Seitz
2014-05-21 17:53 ` Tom Tromey
2014-02-14 8:46 ` [PATCH 05/12] Rename varobj_pretty_printed_p to varobj_is_dynamic_p Yao Qi
2014-04-24 17:39 ` Keith Seitz
2014-05-21 18:02 ` Tom Tromey
2014-02-14 8:46 ` [PATCH 11/12] Test case Yao Qi
2014-04-18 11:45 ` Yao Qi
2014-04-24 20:53 ` Keith Seitz
2014-02-14 8:46 ` [PATCH 08/12] Iterator varobj_items by their availability Yao Qi
2014-04-24 20:28 ` Keith Seitz
[not found] ` <5327A296.3050605@codesourcery.com>
2014-04-04 2:00 ` [RFC 00/12 V2] Visit varobj available children only in MI Yao Qi
2014-04-17 1:12 ` ping : " Yao Qi
2014-04-21 16:20 ` Joel Brobecker
2014-04-22 2:54 ` Yao Qi
2014-06-12 7:37 ` Yao Qi
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=1392367471-13527-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.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