public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gdb-patches@sourceware.org, aburgess@redhat.com
Subject: Re: [PATCH v2] gdb: split array and string limiting options
Date: Tue, 14 Dec 2021 19:24:46 +0200	[thread overview]
Message-ID: <83wnk7je01.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.2112140216110.10183@tpp.orcam.me.uk> (macro@embecosm.com)

> Date: Tue, 14 Dec 2021 16:38:43 +0000 (GMT)
> From: "Maciej W. Rozycki" <macro@embecosm.com>
> Cc: Andrew Burgess <aburgess@redhat.com>
> 
>  gdb/NEWS                                      |   18 +++++++
>  gdb/ada-valprint.c                            |    4 -
>  gdb/c-lang.c                                  |    4 -
>  gdb/c-valprint.c                              |    4 -
>  gdb/doc/gdb.texinfo                           |   36 +++++++++++---
>  gdb/doc/python.texi                           |    5 ++
>  gdb/language.h                                |    2 
>  gdb/m2-lang.c                                 |    2 
>  gdb/m2-valprint.c                             |    3 -
>  gdb/p-lang.c                                  |    2 
>  gdb/p-valprint.c                              |    7 +-
>  gdb/printcmd.c                                |    8 +--
>  gdb/python/py-value.c                         |    6 ++
>  gdb/testsuite/gdb.ada/str_chars.exp           |   64 ++++++++++++++++++++++++++
>  gdb/testsuite/gdb.ada/str_chars/foo.adb       |   26 ++++++++++
>  gdb/testsuite/gdb.base/default.exp            |    4 -
>  gdb/testsuite/gdb.base/examine-backward.exp   |    6 ++
>  gdb/testsuite/gdb.base/options.exp            |    1 
>  gdb/testsuite/gdb.base/printcmds.exp          |   28 +++++------
>  gdb/testsuite/gdb.base/wchar.exp              |    6 +-
>  gdb/testsuite/gdb.base/with.exp               |    2 
>  gdb/testsuite/gdb.guile/scm-pretty-print.exp  |   12 ++--
>  gdb/testsuite/gdb.pascal/str-chars.exp        |   48 +++++++++++++++++++
>  gdb/testsuite/gdb.pascal/str-chars.pas        |   28 +++++++++++
>  gdb/testsuite/gdb.python/py-format-string.exp |   11 ++--
>  gdb/testsuite/gdb.python/py-prettyprint.exp   |    8 ++-
>  gdb/testsuite/lib/gdb.exp                     |    2 
>  gdb/tracepoint.c                              |    4 -
>  gdb/valprint.c                                |   64 ++++++++++++++++++--------
>  gdb/valprint.h                                |   10 ++--
>  30 files changed, 342 insertions(+), 83 deletions(-)
>  create mode 100644 gdb/testsuite/gdb.ada/str_chars.exp
>  create mode 100644 gdb/testsuite/gdb.ada/str_chars/foo.adb
>  create mode 100644 gdb/testsuite/gdb.pascal/str-chars.exp
>  create mode 100644 gdb/testsuite/gdb.pascal/str-chars.pas

Thanks, the documentation parts are OK.

  reply	other threads:[~2021-12-14 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 16:38 Maciej W. Rozycki
2021-12-14 17:24 ` Eli Zaretskii [this message]
2021-12-15 18:01 ` Andrew Burgess
2022-01-04 23:15   ` Maciej W. Rozycki
2022-01-06  7:58 Simon Sobisch
2022-01-06  9:33 ` Andrew Burgess
2022-01-06 13:32   ` Simon Sobisch
2022-01-06 14:18     ` Andrew Burgess
2022-01-26 15:48     ` Maciej W. Rozycki
2022-01-26 16:52       ` Simon Sobisch
2022-01-26 18:18         ` Maciej W. Rozycki

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=83wnk7je01.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@embecosm.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).