From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: richard.bunt@arm.com, Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/2] Add new 'print max-depth' feature
Date: Wed, 27 Mar 2019 21:53:00 -0000 [thread overview]
Message-ID: <cover.1553723416.git.andrew.burgess@embecosm.com> (raw)
To make code review a little easier I split this feature into two
parts, first adding a new field to the language structure, which is
then used in the second commit.
For review purposes you're probably better looking at the second
commit first, hopefully afer that the motivation for the first commit
should be clearer.
--
Andrew Burgess (2):
gdb: Introduce new language field la_struct_too_deep_ellipsis
gdb: Introduce 'print max-depth' feature
gdb/ChangeLog | 42 ++++++
gdb/NEWS | 9 ++
gdb/ada-lang.c | 1 +
gdb/c-lang.c | 4 +
gdb/cp-valprint.c | 32 +++--
gdb/d-lang.c | 1 +
gdb/doc/ChangeLog | 7 +
gdb/doc/gdb.texinfo | 57 ++++++++
gdb/doc/guile.texi | 3 +
gdb/doc/python.texi | 3 +
gdb/f-lang.c | 1 +
gdb/go-lang.c | 1 +
gdb/guile/scm-pretty-print.c | 23 ++-
gdb/language.c | 2 +
gdb/language.h | 5 +
gdb/m2-lang.c | 1 +
gdb/objc-lang.c | 1 +
gdb/opencl-lang.c | 1 +
gdb/p-lang.c | 1 +
gdb/python/py-prettyprint.c | 22 ++-
gdb/rust-lang.c | 1 +
gdb/testsuite/ChangeLog | 12 ++
gdb/testsuite/gdb.base/max-depth.c | 209 +++++++++++++++++++++++++++
gdb/testsuite/gdb.base/max-depth.exp | 122 ++++++++++++++++
gdb/testsuite/gdb.fortran/max-depth.exp | 41 ++++++
gdb/testsuite/gdb.fortran/max-depth.f90 | 40 ++++++
gdb/testsuite/gdb.python/py-nested-maps.c | 122 ++++++++++++++++
gdb/testsuite/gdb.python/py-nested-maps.exp | 211 ++++++++++++++++++++++++++++
gdb/testsuite/gdb.python/py-nested-maps.py | 129 +++++++++++++++++
gdb/testsuite/lib/gdb.exp | 30 ++++
gdb/valprint.c | 66 ++++++++-
gdb/valprint.h | 3 +
32 files changed, 1188 insertions(+), 15 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/max-depth.c
create mode 100644 gdb/testsuite/gdb.base/max-depth.exp
create mode 100644 gdb/testsuite/gdb.fortran/max-depth.exp
create mode 100644 gdb/testsuite/gdb.fortran/max-depth.f90
create mode 100644 gdb/testsuite/gdb.python/py-nested-maps.c
create mode 100644 gdb/testsuite/gdb.python/py-nested-maps.exp
create mode 100644 gdb/testsuite/gdb.python/py-nested-maps.py
--
2.14.5
next prev reply other threads:[~2019-03-27 21:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 23:06 [PATCHv2 0/5] " Andrew Burgess
2019-03-27 21:53 ` Andrew Burgess [this message]
2019-03-27 21:53 ` [PATCH 2/2] gdb: Introduce " Andrew Burgess
2019-03-28 16:08 ` Eli Zaretskii
2019-03-27 21:53 ` [PATCH 1/2] gdb: Introduce new language field la_struct_too_deep_ellipsis Andrew Burgess
2019-03-28 12:43 ` Pedro Alves
2019-03-28 12:47 ` [PATCH 0/2] Add new 'print max-depth' feature Pedro Alves
2019-03-28 22:48 ` Andrew Burgess
2019-03-28 23:47 ` Marco Barisione
2019-04-16 23:06 ` [PATCHv2 1/5] gdb/ada: Update some predicate functions to return bool Andrew Burgess
2019-04-18 0:03 ` Joel Brobecker
2019-04-16 23:06 ` [PATCHv2 5/5] gdb: Introduce 'print max-depth' feature Andrew Burgess
2019-04-17 7:42 ` Philippe Waroquiers
2019-04-17 14:35 ` Eli Zaretskii
2019-04-18 1:07 ` Andrew Burgess
2019-04-18 2:38 ` Eli Zaretskii
2019-04-18 21:52 ` Andrew Burgess
2019-04-19 6:50 ` Eli Zaretskii
2019-04-18 17:08 ` Pedro Alves
2019-04-16 23:06 ` [PATCHv2 2/5] gdb/testsuite: Don't add gcc flags when compiling rust tests Andrew Burgess
2019-04-19 14:31 ` Tom Tromey
2019-04-16 23:06 ` [PATCHv2 3/5] gdb: Introduce new language field la_struct_too_deep_ellipsis Andrew Burgess
2019-04-19 14:37 ` Tom Tromey
2019-04-16 23:06 ` [PATCHv2 4/5] gdb: Introduce new language field la_is_string_type_p Andrew Burgess
2019-04-18 17:08 ` Pedro Alves
2019-04-19 21:00 ` Andrew Burgess
2019-04-19 14:45 ` Tom Tromey
2019-04-19 22:22 ` Andrew Burgess
2019-04-24 19:32 ` Tom Tromey
2019-04-19 22:45 ` Andrew Burgess
2019-04-24 19:33 ` Tom Tromey
2019-04-29 21:14 ` [PATCHv2 0/5] Add new 'print max-depth' feature Andrew Burgess
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=cover.1553723416.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=richard.bunt@arm.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