From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Paul Hilfinger <Hilfinger@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Have block_innermost_frame start from selected frame
Date: Wed, 28 Dec 2011 17:23:00 -0000 [thread overview]
Message-ID: <20111228162936.GO23376@adacore.com> (raw)
In-Reply-To: <20111228155657.GA10556@host2.jankratochvil.net>
> I find that GDB should ask or at least warn more in general.
OK, I see why you are suggesting queries and menus, now.
I think that generally speaking, we're trying to be less verbose,
to make sure that any important message does not get drowned as
you explain. Similarly, I would like us to limit the number of
queries and menus to the minimum as well. That's why the
multiple-symbols setting is set to "all" rather than "ask", for
instance. I realize it's a matter of opinion, and people can
easily disagree. No problem.
But I think we can easily do without the query here. As I said,
the old behavior can be reproduced. The new behavior is more versatile.
And, to me at least, and the few at AdaCore who discussed this,
we all concluded that the new behavior made more sense than the old.
> > It's the only way to get the value of "var" in our testcase, and you
> > cannot currently do it with the old behavior.
>
> You can already do so many things with GDB, just people do not do even
> 5% of them because it is all too magic to learn.
You are probably right, but following your logic, we should dumb GDB
down. Many times, that's a good thing, I agree. But I don't think
that's always the case. And I do think that it goes against general
usability in our situation.
--
Joel
next prev parent reply other threads:[~2011-12-28 16:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 19:59 Paul Hilfinger
2011-12-28 13:10 ` Jan Kratochvil
2011-12-28 15:41 ` Joel Brobecker
2011-12-28 16:00 ` Jan Kratochvil
2011-12-28 17:23 ` Joel Brobecker [this message]
2011-12-29 20:30 ` Paul Hilfinger
2011-12-29 23:13 ` Jan Kratochvil
2011-12-28 15:16 ` Jan Kratochvil
2011-12-30 21:54 Paul Hilfinger
2011-12-31 8:58 ` Eli Zaretskii
2011-12-31 21:40 ` Paul Hilfinger
2012-01-09 7:17 ` Paul Hilfinger
2012-01-09 17:14 ` Eli Zaretskii
2012-01-09 19:59 ` Paul Hilfinger
2012-01-10 5:21 ` Joel Brobecker
2012-01-10 10:28 ` Eli Zaretskii
2012-01-10 10:40 ` Joel Brobecker
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=20111228162936.GO23376@adacore.com \
--to=brobecker@adacore.com \
--cc=Hilfinger@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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).