From: Tom Tromey <tromey@adacore.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [pushed] Invert test in gdb.ada/ptype_tagged_param.exp
Date: Fri, 27 Jan 2023 14:01:10 -0700 [thread overview]
Message-ID: <87r0vfpu95.fsf@tromey.com> (raw)
In-Reply-To: <89869c3c-0a4f-67e3-dd98-13ea090b31c6@palves.net> (Pedro Alves's message of "Fri, 27 Jan 2023 20:15:47 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:
>> kfail "no debug info" $gdb_test_name
Pedro> Why is this a kfail instead of an xfail? Is there really a GDB bug here?
It's just my perennial inability to distinguish the two. There's no gdb
bug, this seems to be a compiler issue. If changing it to xfail is
correct, let me know and I will do it. And endeavor to remember that
kfail is for gdb bugs.
Tom
next prev parent reply other threads:[~2023-01-27 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 17:24 Tom Tromey
2023-01-27 20:15 ` Pedro Alves
2023-01-27 21:01 ` Tom Tromey [this message]
2023-01-27 21:11 ` Pedro Alves
2023-01-30 15:03 ` Tom Tromey
2023-01-30 15:22 ` Pedro Alves
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=87r0vfpu95.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).