From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
gdb-patches <gdb-patches@sourceware.org>,
Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [obv] compile-print.exp: xfail->kfail for '@' GDB array operator
Date: Fri, 05 Jun 2015 15:19:00 -0000 [thread overview]
Message-ID: <CADPb22RdmOyA+ryQVmKYMxPpsBRvnkWOnkmS2PQ4F05xa-VShA@mail.gmail.com> (raw)
In-Reply-To: <20150605124035.GA1995@host1.jankratochvil.net>
On Fri, Jun 5, 2015 at 5:40 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> 'compile print' should one day replace the standard 'print' command, like in
> LLDB. Otherwise 'compile print' makes no sense.
Just so we're on the same page,
the plan isn't to remove the "standard 'print' command", right?
[The print (output, etc.) commands would either use the builtin
support or compile print.]
next prev parent reply other threads:[~2015-06-05 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 19:38 Jan Kratochvil
2015-06-05 9:35 ` Yao Qi
2015-06-05 12:40 ` Jan Kratochvil
2015-06-05 15:19 ` Doug Evans [this message]
2015-06-05 15:26 ` Jan Kratochvil
2015-06-05 16:13 ` Yao Qi
2015-06-05 21:23 ` Jan Kratochvil
2015-06-05 13:24 ` Jan Kratochvil
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=CADPb22RdmOyA+ryQVmKYMxPpsBRvnkWOnkmS2PQ4F05xa-VShA@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.com \
--cc=qiyaoltc@gmail.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