From: Christopher Faylor <cgf-rcm@redhat.com>
To: gilbert buob <gilbert.buob@sciopta.com>,
"insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: slow response time when debugging over ethernet
Date: Sat, 07 Jun 2003 15:39:00 -0000 [thread overview]
Message-ID: <20030607153937.GA24790@redhat.com> (raw)
In-Reply-To: <1054932864.1831.15.camel@lindt.uglyboxes.com>
On Fri, Jun 06, 2003 at 01:54:24PM -0700, Keith Seitz wrote:
>On Wed, 2003-06-04 at 04:49, gilbert buob wrote:
>
>> do you know this problem,?
>> I also loocking for a work around ( just download over tcp and the debug
>> over serial)
>> I also shall contact the gdb mailing list because it seem to be a window-gdb
>> problem
>
>Hmm. Could be a cygwin bug, too, I suppose. Maybe TCP_NODELAY isn't
>working?
If it is working in Windows winsock implementation then it should be working in
Cygwin.
cgf
prev parent reply other threads:[~2003-06-07 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 8:56 gilbert buob
2003-05-23 12:03 ` Keith Seitz
2003-06-04 11:50 ` gilbert buob
2003-06-06 20:47 ` Keith Seitz
2003-06-07 15:39 ` Christopher Faylor [this message]
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=20030607153937.GA24790@redhat.com \
--to=cgf-rcm@redhat.com \
--cc=gilbert.buob@sciopta.com \
--cc=insight@sources.redhat.com \
--cc=insight@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).