From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add missing TYPE_CODE_* constants to Python
Date: Fri, 14 Oct 2022 20:45:35 +0300 [thread overview]
Message-ID: <83y1ti70zk.fsf@gnu.org> (raw)
In-Reply-To: <20221014163950.920834-1-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Fri, 14 Oct 2022 10:39:50 -0600)
> Date: Fri, 14 Oct 2022 10:39:50 -0600
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Tom Tromey <tromey@adacore.com>
>
> A user noticed that TYPE_CODE_FIXED_POINT was not exported by the gdb
> Python layer. This patch fixes the bug, and prevents future
> occurences of this type of bug.
> ---
> gdb/doc/guile.texi | 13 +++++
> gdb/doc/python.texi | 13 +++++
> gdb/gdbtypes.h | 114 +------------------------------------
> gdb/guile/scm-type.c | 35 ++----------
> gdb/python/py-type.c | 37 +++---------
> gdb/type-codes.def | 131 +++++++++++++++++++++++++++++++++++++++++++
> 6 files changed, 173 insertions(+), 170 deletions(-)
> create mode 100644 gdb/type-codes.def
OK for the documentation parts, thanks.
next prev parent reply other threads:[~2022-10-14 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 16:39 Tom Tromey
2022-10-14 17:45 ` Eli Zaretskii [this message]
2022-10-31 18:47 ` Tom Tromey
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=83y1ti70zk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).