From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [cancel] [patch] More suggestive error_is_running message
Date: Tue, 17 Apr 2012 21:26:00 -0000 [thread overview]
Message-ID: <20120417212234.GA21359@host2.jankratochvil.net> (raw)
In-Reply-To: <20120411164522.GE2852@adacore.com>
On Wed, 11 Apr 2012 18:45:22 +0200, Joel Brobecker wrote:
> In any case, as I said, I don't have a strong opinion. I know that
> we want to both have concise error messages, while at the same time
> making GDB more explanatory on some confusing or tricky situations.
> This is a real conundrum.
In general GDB should always suggest possible solutions to a problem.
Stating just the problem may not be enough for the user.
This is like GDB says just "(no debugging symbols found)" but Fedora GDB says
also:
Missing separate debuginfos, use: debuginfo-install bc-1.06.95-3.fc15.x86_64
considered good in:
http://lists.fedoraproject.org/pipermail/devel/2012-April/165756.html
This is why I tried to suggest (one of) a possible solutions to the problem,
but it somehow did not go in, maintaining all these messages downstream is
expensive.
Regards,
Jan
next prev parent reply other threads:[~2012-04-17 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 19:20 Jan Kratochvil
2012-04-10 21:30 ` Sergio Durigan Junior
2012-04-11 2:16 ` Jan Kratochvil
2012-04-11 4:55 ` Sergio Durigan Junior
2012-04-12 15:28 ` Tom Tromey
2012-04-11 15:35 ` Joel Brobecker
2012-04-11 15:48 ` [cancel] " Jan Kratochvil
2012-04-11 17:17 ` Joel Brobecker
2012-04-17 21:26 ` Jan Kratochvil [this message]
2012-04-17 23:01 ` 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=20120417212234.GA21359@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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