From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Hannes Domani <ssbssa@yahoo.de>, gdb-patches@sourceware.org
Subject: Re: [OBV] [PATCH] Fix pretty printer of main_type.flds_bnds.bounds
Date: Sat, 2 Jan 2021 13:43:21 -0500 [thread overview]
Message-ID: <fff0948e-b20f-0557-35b1-b56b5007ddec@polymtl.ca> (raw)
In-Reply-To: <20210102183852.2029-1-ssbssa@yahoo.de>
On 2021-01-02 1:38 p.m., Hannes Domani via Gdb-patches wrote:
> I will push this under the obvious rule.
>
>
> In struct dynamic_prop the members kind and data were rename to m_kind and
> m_data.
>
> And flag_upper_bound_is_count is actually in bounds directly, not in its
> high member.
>
> gdb/ChangeLog:
>
> 2021-01-02 Hannes Domani <ssbssa@yahoo.de>
>
> * gdb-gdb.py.in: Fix main_type.flds_bnds.bounds pretty printer.
Thanks for doing this. We don't have any tests exercising these, so I
always forget to update them.
Simon
prev parent reply other threads:[~2021-01-02 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210102183852.2029-1-ssbssa.ref@yahoo.de>
2021-01-02 18:38 ` Hannes Domani via Gdb-patches
2021-01-02 18:43 ` Simon Marchi via Gdb-patches [this message]
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=fff0948e-b20f-0557-35b1-b56b5007ddec@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=ssbssa@yahoo.de \
/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