From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remote UDP support
Date: Sun, 12 May 2002 21:44:00 -0000 [thread overview]
Message-ID: <3CDF449F.7020300@cygnus.com> (raw)
In-Reply-To: <20020513012154.GB17951@nevyn.them.org>
> How's this look? I wasn't quite sure what to put in the text of the
>> >warning. Also added one to the manual.
>
>>
>> Problem is, its in the wrong place, and I suspect getting it into the
>> right place - remote.c - is tricky.
>>
>> I think adding a FIXME hack to remote.c (search for serial_open) that
>> checks for ``udp:'' and then print a warning is the most pratical.
>
>
> I don't understand. Why hoist it up into remote.c, before each call to
> serial_open? That just descends through serial_open to call net_open
> and the warning would arrive at the same position; the warning is
> specific to ser-tcp, and seems to belong there.
Sorry, yes the rationale was a big bit vague :-(
serial_open() provides a generic serial connection. Data that goes in
one end, hopefully, comes out the other end - it doesn't promise to be
reliable though.
remote.c, on the other hand, makes certain assumptions about the
properties of the SERIAL object it is using (only data overrun is
possible, single character transfers are reliable, ...). Hence, I think
remote.c should be the one reporting a potential problem.
Besides, if someone were to implement a remote-udp.c the warning would
be wrong :-)
enjoy,
Andrew
next prev parent reply other threads:[~2002-05-13 4:44 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
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 [this message]
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=3CDF449F.7020300@cygnus.com \
--to=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