Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Michael Snyder <msnyder@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remote UDP support
Date: Thu, 09 May 2002 20:51:00 -0000	[thread overview]
Message-ID: <np1yckbqyc.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3CDAF7B7.3020904@cygnus.com>


Andrew Cagney <ac131313@cygnus.com> writes:
> > On Thu, May 09, 2002 at 05:18:02PM -0400, Andrew Cagney wrote:
> >
> >> >Andrew, would you be satisfied with a warning in the manual and a
> >> >warning in 'help target remote'?
> >
> >> No.  I think it need to be in the users face.  I don't think GDB
> >> should silently let the user to use a broken mechanism.
> > I really don't agree, but your call.  Could I at least persuade you
> > down to a one-line warning and no confirmation query?
> > Requiring a separate confirmation just seems like a bad interface
> > decision.
> 
> It is relative.  Adding a feature to GDB that will make GDB unreliable
> and then failing to alert the user of the consequences is, I think, a
> worse decision.  The user is no longer able to depend on the debuger -
> something critically important for someone debugging an embedded
> application.
> 
> Can you please update the patch to include a mechanism for querying
> the user (just the first time) to confirm that they know and
> understand that the mechanism is unreliable (including a brief
> statement of known failure states).

I really disagree with this.  It's fine to print a one-line warning
--- something that doesn't interrupt the user's train of thought.  But
people aren't going to type "target remote udp:..." by accident.

Whenever I've said, "UDP isn't reliable!", nobody has ever reacted
with shock --- "You're kidding!  It isn't?"  They always say, "Yes, I
know, and I don't care."



  reply	other threads:[~2002-05-10  3:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08 16:26 Daniel Jacobowitz
2002-05-08 16:58 ` Michael Snyder
2002-05-08 17:11   ` Daniel Jacobowitz
2002-05-08 21:52     ` Eli Zaretskii
2002-05-08 17:39 ` Andrew Cagney
2002-05-08 17:53   ` Daniel Jacobowitz
2002-05-08 19:56     ` Andrew Cagney
2002-05-08 20:01       ` Daniel Jacobowitz
2002-05-09 11:37         ` Michael Snyder
2002-05-09 11:44           ` Daniel Jacobowitz
2002-05-09 14:18             ` Andrew Cagney
2002-05-09 14:20               ` Daniel Jacobowitz
2002-05-09 15:27                 ` Andrew Cagney
2002-05-09 20:51                   ` Jim Blandy [this message]
2002-05-09 21:28                     ` Jason R Thorpe
2002-05-09 21:45                     ` Andrew Cagney
2002-05-09 22:32                       ` Jason R Thorpe
2002-05-10  8:18                       ` Frank Ch. Eigler
2002-05-10 13:54                         ` Andrew Cagney
2002-05-10 13:57                           ` Jason R Thorpe
2002-05-10 14:07                           ` Martin M. Hunt
2002-05-11 12:12                 ` Andrew Cagney
2002-05-11 14:32                   ` Daniel Jacobowitz
2002-05-11 15:01                     ` Andrew Cagney
2002-05-12 18:22                       ` Daniel Jacobowitz
2002-05-12 21:44                         ` Andrew Cagney
2002-05-13 10:42                           ` Daniel Jacobowitz
2002-05-13 14:06                             ` Andrew Cagney
2002-05-13 21:32                               ` Daniel Jacobowitz

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=np1yckbqyc.fsf@zwingli.cygnus.com \
    --to=jimb@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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