From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix crash in cp_print_value_fields
Date: Wed, 29 May 2019 15:34:00 -0000 [thread overview]
Message-ID: <87blzlz33s.fsf@tromey.com> (raw)
In-Reply-To: <20190517201814.27951-1-tromey@adacore.com> (Tom Tromey's message of "Fri, 17 May 2019 14:18:14 -0600")
Tom> 2019-05-17 Tom Tromey <tromey@adacore.com>
Tom> PR c++/20020:
Tom> * cp-valprint.c (cp_print_value_fields): Call
Tom> cp_print_static_field inside "try".
I'm checking this in now.
Tom
next prev parent reply other threads:[~2019-05-29 15:34 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 [this message]
2019-05-29 19:20 ` Pedro Alves
2019-06-18 15:34 ` Tom Tromey
2019-06-18 13:50 ` Tom de Vries
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=87blzlz33s.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
/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