Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Martin M. Hunt" <hunt@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>,
	"Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remote UDP support
Date: Fri, 10 May 2002 14:07:00 -0000	[thread overview]
Message-ID: <200205101406.13808.hunt@redhat.com> (raw)
In-Reply-To: <3CDC337D.4050407@cygnus.com>

On Friday 10 May 2002 01:54 pm, Andrew Cagney wrote:
> > cagney wrote:
> >> [...]
> >> I think there is a subtle difference between someone understanding
> >> that ``UDP is unreliable'' and someone understanding that the remote
> >> protocol doesn't work across UDP.
> >> [...]
> >
> > It seems that this train of thought indicates a self-contradictory
> > attitude.  Either the remote protocol is "good enough" over udp, or it
> > isn't.  If on one hand you think it's good enough to be included
> > within mainline gdb, then don't argue that it's not good enough to
> > actually work.
>
> Not really.
>
> UDP across the loopback interface is 100% reliable.  Across cheap
> overloaded thin-wire definitly isn't.  

Not true, but not important.

I don't understand what the fuss is about.  The "users" for UDP are not 
clueless people who are going to accidently connect to a target with UDP.  
They are probably embedded engineers trying to get new hardware running with 
GDB ASAP. So warn them, but there is no reason to harrass them.

-- 
Martin Hunt
GDB Engineer
Red Hat, Inc.


  parent reply	other threads:[~2002-05-10 21:07 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
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 [this message]
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=200205101406.13808.hunt@redhat.com \
    --to=hunt@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=fche@redhat.com \
    --cc=gdb-patches@sources.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