Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [unavailable regs/locals, 01/11] registers status upwards
Date: Thu, 17 Mar 2011 17:25:00 -0000	[thread overview]
Message-ID: <20110317163126.GA27867@host1.jankratochvil.net> (raw)
In-Reply-To: <201103171621.48928.pedro@codesourcery.com>

On Thu, 17 Mar 2011 17:21:48 +0100, Pedro Alves wrote:
> Another key point, is that not putting a TRY_CATCH were it would matter
> is fragile as well.  The whole operation is cancelled.  It makes the whole
> user experience _worse_.  Seing 0s is worse than <unavailable> at places,
> but it's much better than not seeing _anything_ at all.  E.g, the MI
> command I showed upthread.

Here is probably the major disagreement.  People bugreport when they see error
while they give up when the program does weird things they cannot understand.


> How about proceeding as is, and I'll revisit later if necessary?
> This is just _one_ detail in the whole story afterall.

I do not want to block anything.  But in such case a review does not make
sense as it is easier to put there compiler and/or exception checks than to
verify each statement by humans.


Thanks,
Jan


  reply	other threads:[~2011-03-17 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 13:28 Pedro Alves
2011-02-28 15:53 ` Jan Kratochvil
2011-03-16  1:40   ` Pedro Alves
2011-03-17 16:31     ` Jan Kratochvil
2011-03-17 16:48       ` Pedro Alves
2011-03-17 17:25         ` Jan Kratochvil [this message]
2011-03-17 19:15           ` Pedro Alves
2011-03-28 21:17       ` Tom Tromey

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=20110317163126.GA27867@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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