From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@adacore.com>,
gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Fix crash in cp_print_value_fields
Date: Tue, 18 Jun 2019 15:34:00 -0000 [thread overview]
Message-ID: <874l4mlxfg.fsf@tromey.com> (raw)
In-Reply-To: <c3f7e9be-d26e-2b60-04ab-aab48b6ead4e@redhat.com> (Pedro Alves's message of "Wed, 29 May 2019 20:19:59 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> On 5/17/19 9:18 PM, Tom Tromey wrote:
>> +# "x" sometimes isn't available due to
>> +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90526
>> +gdb_test "print x" " = {static f = .*}"
>> +
Pedro> How about making that expect the correct value, and then use
Pedro> "setup_xfail gcc/90526" ?
Sorry about the delay on this. I made this change, and I'll send it soon.
Tom
next prev parent reply other threads:[~2019-06-18 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
2019-05-29 19:20 ` Pedro Alves
2019-06-18 15:34 ` Tom Tromey [this message]
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=874l4mlxfg.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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