Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remote UDP support
Date: Wed, 08 May 2002 17:53:00 -0000	[thread overview]
Message-ID: <20020509005348.GA14040@nevyn.them.org> (raw)
In-Reply-To: <3CD9C53D.5060704@cygnus.com>

On Wed, May 08, 2002 at 08:39:25PM -0400, Andrew Cagney wrote:
> >A patch for this feature was supported a year or so ago, but never went 
> >in. 
> 
> (lack of assignment the last time it was posted from memory).

Yep.

> >I had a need for this a couple of days ago, so I did it over from scratch;
> >it's much easier now than it was at the time.  The name of ser-tcp.c is a
> >bit wrong after this patch; I can either rename the file to ser-net.c or
> >just update some comments to match.  Got a preference?  Otherwise OK?
> 
> From memory, the last time this came up the conclusion was that:

I didn't see any of these conclusions when I looked.  Oh well.  None of
them were in the thread with the original patch or the discussion about
queuing it for 5.1.

> - It isn't at all reliable (rather than mostly reliable as across TCP or 
> serial).  The entire ``T'' stop packet can be lost and neither GDB, nor 
> the target, would notice.

Certainly.  I also see a comment about the G packet needing to fit in
one UDP packet, although I'm not 100% sure that's right.

> - it wasn't necessary - there are micro tcp implementations around that 
> implement sufficient TCP for the remote protocol to work

Still bigger than a polled UDP implementation, and much more
complicated.  Implementing a tiny UDP stack is simple!  Sure, it isn't
reliable at all; so use it on small networks and be careful :)

> Check the archives (search for mark salter?).

You vastly overestimate ht:/Dig if you think that's possible.  I really
want that program killed.

> One theory put forward was to have GDB print a banner(6) sized warning 
> (and get confirmation) before accepting the option.

I have to admit, I don't see the point.  A big warning in the
documentation, maybe, but such a confirmation query would drive me
crazy if I actually needed to use this regularly.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-05-09  0:53 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 [this message]
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
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=20020509005348.GA14040@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.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