slow response time when debugging over ethernet

slow response time when debugging over ethernet

[gilbert buob]

hello

I use insight and want to debug a remote target using redboot on the
remote target. The remote target is powered with a pentium. When I use
the serial port for debugging, response time is correct, Now I use
ethernet, for the download, it is very fast. but when I debug the target

the response time is very very slow. Insight is installed  on a NT4
station and use cygwin. insight 5.1.1 and is configured as
"host=i686-pc-cygwin target=i386-elf"

do you know this problem ?

thank
gilbert

Re: slow response time when debugging over ethernet

[Keith Seitz]

On Thu, 2003-05-22 at 01:55, gilbert buob wrote:
> the response time is very very slow. Insight is installed  on a NT4
> station and use cygwin. insight 5.1.1 and is configured as
> "host=i686-pc-cygwin target=i386-elf"

I haven't any idea why off the top of my head. That version is very,
very old.

Before we get into profiling or stepping through the code to see what it
is doing, please try debugging over ethernet with command line gdb.
Let's rule out any obvious gdb problems.

Keith

Re: slow response time when debugging over ethernet

[gilbert buob]

Following your suggestion, I have made some trials to debug over ethernet
with command line gdb .
I made two test , one with gdb5.1.1/host NT4/ remote target i386-elf and one
with cygwin package gdb ( last one) /host w2k/remote target i386-elf..Remote
target monitor is redboot.  Result is the same as with Insight <--> the
problem is on gdb : The download is very fast but debugging is slow.We also
have made the trial with a Linux platform as host and then response time is
OK <--> the problem is connected with window.
Then we also have analysed the network traffic ( with ethreal) during the
debugging  session in both case. I t seems that when using host = window we
have a delay due to the naggle algo of tcp level. This delay should be off
when using little packet ( this occurs when debugging ). On the host=linux
the delay is off.

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

Gilbert

Keith Seitz schrieb:

> On Thu, 2003-05-22 at 01:55, gilbert buob wrote:
> > the response time is very very slow. Insight is installed  on a NT4
> > station and use cygwin. insight 5.1.1 and is configured as
> > "host=i686-pc-cygwin target=i386-elf"
>
> I haven't any idea why off the top of my head. That version is very,
> very old.
>
> Before we get into profiling or stepping through the code to see what it
> is doing, please try debugging over ethernet with command line gdb.
> Let's rule out any obvious gdb problems.
>
> Keith

Re: slow response time when debugging over ethernet

[Keith Seitz]

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?

I'd ask about it on the gdb list, though. That'll get you further. I
would also include a command line session showing the problem (as best
as possible) with remote debugging on (set debug remote 1/set
remotedebug 1).

Keith

Re: slow response time when debugging over ethernet

[Christopher Faylor]

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