From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, Eli Zaretskii <eliz@gnu.org>
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Implement show | set can-call-inferior-functions [on|off]
Date: Thu, 25 Apr 2019 19:44:00 -0000 [thread overview]
Message-ID: <5fcb52fe-655b-f9b9-ab4c-21ef54a67b88@redhat.com> (raw)
In-Reply-To: <87bm0udy4r.fsf@tromey.com>
On 4/25/19 2:15 PM, Tom Tromey wrote:
> An error definitely seems like the correct thing to do here. Other
> choices will give silently mysterious behavior.
>
> A convenience variable is fine, too, though I suspect it will be little
> used. I wouldn't require it for this patch to go in.
Agreed. You could argue that it'd be better to instead come up with
a facility for CLI to inspect the value of any set/show option, though.
But you can already do that with Python's gdb.parameter, so I
guess it may not be that pressing to have a pure CLI mechanism.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-04-25 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 21:58 Philippe Waroquiers
2019-04-24 6:53 ` Eli Zaretskii
2019-04-24 21:25 ` Philippe Waroquiers
2019-04-25 6:12 ` Eli Zaretskii
2019-04-25 13:15 ` Tom Tromey
2019-04-25 19:44 ` Pedro Alves [this message]
2019-04-25 17:17 ` 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=5fcb52fe-655b-f9b9-ab4c-21ef54a67b88@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).