Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [cancel] [patch] More suggestive error_is_running message
Date: Wed, 11 Apr 2012 17:17:00 -0000	[thread overview]
Message-ID: <20120411164522.GE2852@adacore.com> (raw)
In-Reply-To: <20120411153457.GA22022@host2.jankratochvil.net>

> The whole point of my patch was not notify about the _wait_, not about
> the _interrupt_, as this is what one cannot easily catch when
> debugging a testcase after converting it full-stop -> non-stop.  If
> you try to reproduce the problem by hand it works.  OK, I admit I am
> too stupid to write GDB testcases.

I missed a bit the context leading to the improvement you were
suggesting, but it was not my intention to say that you are "too
stupid to [...]" at all. This sounds like a harsh criticism of
yourself - perhaps a quirk of English not being our native language
for both of us.

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.

-- 
Joel


  reply	other threads:[~2012-04-11 16:45 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 [this message]
2012-04-17 21:26       ` Jan Kratochvil
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=20120411164522.GE2852@adacore.com \
    --to=brobecker@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