From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Improve help test for commands defined in Python
Date: Tue, 17 May 2022 11:51:43 +0100 [thread overview]
Message-ID: <cover.1652784658.git.aburgess@redhat.com> (raw)
Patch #1 is a small refactor ahead of patch #2.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb: use gdb::unique_xmalloc_ptr<char> for docs in cmdpy_init
gdb/python: improve formatting of help text for user defined commands
gdb/NEWS | 6 +
gdb/python/py-cmd.c | 16 +-
gdb/python/py-param.c | 2 +
gdb/python/py-utils.c | 198 +++++++++++++
gdb/python/python-internal.h | 21 ++
gdb/testsuite/gdb.python/py-doc-reformat.exp | 278 +++++++++++++++++++
6 files changed, 513 insertions(+), 8 deletions(-)
create mode 100644 gdb/testsuite/gdb.python/py-doc-reformat.exp
--
2.25.4
next reply other threads:[~2022-05-17 10:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:51 Andrew Burgess via Gdb-patches [this message]
2022-05-17 10:51 ` [PATCH 1/2] gdb: use gdb::unique_xmalloc_ptr<char> for docs in cmdpy_init Andrew Burgess via Gdb-patches
2022-05-26 17:43 ` Tom Tromey
2022-05-28 10:10 ` Andrew Burgess via Gdb-patches
2022-05-17 10:51 ` [PATCH 2/2] gdb/python: improve formatting of help text for user defined commands Andrew Burgess via Gdb-patches
2022-05-17 12:19 ` Eli Zaretskii via Gdb-patches
2022-05-17 22:41 ` Lancelot SIX via Gdb-patches
2022-05-18 10:19 ` Andrew Burgess via Gdb-patches
2022-05-18 12:09 ` Eli Zaretskii via Gdb-patches
2022-05-26 17:46 ` Tom Tromey
2022-05-28 10:11 ` Andrew Burgess via Gdb-patches
2022-05-31 21:54 ` Carl Love via Gdb-patches
2022-05-31 23:10 ` Carl Love via Gdb-patches
2022-06-03 18:05 ` Carl Love via Gdb-patches
2022-06-06 11:40 ` [PUSHED] gdb/testsuite: add missing skip_python_tests call in py-doc-reformat.exp Andrew Burgess via Gdb-patches
2022-06-07 16:08 ` Carl Love via Gdb-patches
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.1652784658.git.aburgess@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=aburgess@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