From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Fix crash in cp_print_value_fields
Date: Tue, 18 Jun 2019 13:50:00 -0000 [thread overview]
Message-ID: <d7a187c4-df58-88b7-5763-003447aae181@suse.de> (raw)
In-Reply-To: <20190517201814.27951-1-tromey@adacore.com>
On 17-05-19 22:18, Tom Tromey wrote:
> From: Tom Tromey <tom@tromey.com>
>
> PR c++/20020 concerns a crash in cp_print_value_fields. The immediate
> cause is that cp_print_value_fields does not handle the case where
> value_static_field fails. This is fixed in this patch by calling
> cp_print_static_field from the "try" block.
>
> Digging a bit deeper, the error occurs because GCC does not emit a
> DW_AT_const_value for a static constexpr member appearing in a
> template class. I've filed a GCC bug for this.
>
> Tested on x86-64 Fedora 29.
>
> gdb/ChangeLog
> 2019-05-17 Tom Tromey <tromey@adacore.com>
>
> PR c++/20020:
> * cp-valprint.c (cp_print_value_fields): Call
> cp_print_static_field inside "try".
>
> gdb/testsuite/ChangeLog
> 2019-05-17 Tom Tromey <tromey@adacore.com>
>
> PR c++/20020:
> * gdb.cp/constexpr-field.exp: New file.
> * gdb.cp/constexpr-field.cc: New file.
> ---
> gdb/ChangeLog | 6 ++++
> gdb/cp-valprint.c | 12 ++++----
> gdb/testsuite/ChangeLog | 6 ++++
> gdb/testsuite/gdb.cp/constexpr-field.cc | 37 ++++++++++++++++++++++++
> gdb/testsuite/gdb.cp/constexpr-field.exp | 36 +++++++++++++++++++++++
> 5 files changed, 90 insertions(+), 7 deletions(-)
> create mode 100644 gdb/testsuite/gdb.cp/constexpr-field.cc
> create mode 100644 gdb/testsuite/gdb.cp/constexpr-field.exp
>
> diff --git a/gdb/cp-valprint.c b/gdb/cp-valprint.c
> index ff860df499a..d8d5c06fd1e 100644
> --- a/gdb/cp-valprint.c
> +++ b/gdb/cp-valprint.c
> @@ -329,22 +329,20 @@ cp_print_value_fields (struct type *type, struct type *real_type,
> }
> else if (field_is_static (&TYPE_FIELD (type, i)))
> {
> - struct value *v = NULL;
> -
> try
> {
> - v = value_static_field (type, i);
> - }
> + struct value *v = value_static_field (type, i);
>
> + cp_print_static_field (TYPE_FIELD_TYPE (type, i),
> + v, stream, recurse + 1,
> + options);
> + }
Here options is used ...
> catch (const gdb_exception_error &ex)
> {
> fprintf_filtered (stream,
> _("<error reading variable: %s>"),
> ex.what ());
> }
> -
> - cp_print_static_field (TYPE_FIELD_TYPE (type, i),
> - v, stream, recurse + 1, opts);
while here opts used to be used.
Is this change intentional? It's not mentioned anywhere.
Thanks,
- Tom
> }
> else if (i == vptr_fieldno && type == vptr_basetype)
> {
next prev parent reply other threads:[~2019-06-18 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 20:18 Tom Tromey
2019-05-29 15:34 ` Tom Tromey
2019-05-29 19:20 ` Pedro Alves
2019-06-18 15:34 ` Tom Tromey
2019-06-18 13:50 ` Tom de Vries [this message]
2019-06-18 15:35 ` Tom Tromey
2019-08-02 15:14 ` [8.3 backport] " Tom de Vries
2019-08-02 17:27 ` 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=d7a187c4-df58-88b7-5763-003447aae181@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--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