From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remote UDP support
Date: Thu, 09 May 2002 11:37:00 -0000 [thread overview]
Message-ID: <3CDABEB1.5008A502@redhat.com> (raw)
In-Reply-To: <20020509030123.GA7864@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> On Wed, May 08, 2002 at 10:56:35PM -0400, Andrew Cagney wrote:
> > >>- 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 :)
> >
> > >>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.
> >
> > That is the point! I don't want to be around when someone that (shock
> > horror :-) fails to read the manual and then complains that the GDB
> > remote protocol isn't reliable. What about a:
>
> The only place I documented the syntax is in the manual. Good luck
> finding it otherwise :)
"help target remote"?
> > set remote
> > i-do-not-understand-gdb-remote-protocol-and-foolishly-think-udp-works-so-please-enable-it
> > on
> >
> > option.
> >
> > Have you tried running the testsuite across UDP?
>
> Have you tried running the testsuite with gdbserver on a remote
> machine? :P
Yes, it was certainly working some time (recently too, I think).
Have you looked at testsuite/config/gdbserver.exp?
next prev parent reply other threads:[~2002-05-09 18:37 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 [this message]
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=3CDABEB1.5008A502@redhat.com \
--to=msnyder@redhat.com \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.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