[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Re: [lwip] TCP xfer halting
|
From: |
Chris Borrelli |
|
Subject: |
[lwip-users] Re: [lwip] TCP xfer halting |
|
Date: |
Wed, 08 Jan 2003 23:46:28 -0000 |
--------------020402030602030002010500
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
I ran into this as well. There are some variables in the pcb structure
that are 8-bit or 16-bit. I changed all of these to 32-bit integers.
That seemed to clear things up. Here is what Paul suggested when I was
having this problem: (from the "Re: [lwip] lwip (current): large data
transfers seem to break lwip" thread)
>to find this bug is laborious, but straight forward
>
>do the following:
>
>create a loooong printf statement that dumps the
>state of the tcp pcb structure at every packet.
>you should print the decimal/hex value of every
>structure member
>
>dump the whole thing to a log file, and see
>what happens just before the stack dies
>
>most probably, there is a tell-tail sign like
>a wrapping parameter
>
>i have found a bug this way before, but it may
>not be the same bug.
>
>you can also see what members i have changed to
>be 32-bit at paulos.2038bug.com
>
>-paul
>
-Chris
address@hidden (added by color.sics.se) wrote:
>We had some problems sending large data arrays but our fix was to change the
>netconn_write function argument size from u16_t to u32_t.
>
>Tim
>
>-----Original Message-----
>From: Kevin Stokes [mailto:address@hidden
>Sent: jeudi, 31. octobre 2002 22:56
>To: address@hidden
>Subject: [lwip] TCP xfer halting
>
> I'm using version 0.5.3 of LWIP running on pure DOS (ie, not a DOS box
>under Windows), compiled with DJGPP.
>
> Connections go ok, and every seems good until I start to send some large
>data arrays.
>
> After sending 4125 packets and 4193333 bytes of data, LWIP stops sending
>data on that port. It does not crash, and the stats seem ok. Other ports
>are still working fine.
>
> It is just sitting there with tcp_sndbuf() always returning a value of 0
>bytes, so no more data gets sent to tcp_write().
>
> The Windows program running on the other end of the ethernet cable is
>waiting for more data, and not crashed.
>
> Two questions:
>
> 1.) Have other people experienced this with LWIP? Is there a solution or
>a bug fix for it?
>
> 2.) If not, does anybody have any suggestions for where to start in
>finding the problem?
>
> I really like LWIP, and have been lurking on the mailing list for about 5
>months.
>
> Thanks very much,
>
> -Kevin Stokes
>
>
>
>
>
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.384 / Virus Database: 216 - Release Date: 8/21/2002
>
>
>[This message was sent through the lwip discussion list.]
>
>
>------------------------------------------------------------------------
>
>************************************************************************************
>This e-mail message is intended only for the addressee(s) and contains
>information which may be confidential. If you are not the intended
>recipient please do not read, save, forward, disclose or copy the contents
>of this e-mail. If this e-mail has been sent to you in error, please delete
>this
>e-mail and any copies or links to this e-mail completely and immediately
>from your system. We also like to inform you that communication via e-mail
>over the Internet is insecure because third parties may have the possibility
>to access and manipulate e-mails.
>
>Any views expressed in this message are those of the individual sender,
>except where the sender specifically states them to be the views of
>The Swatch Group Ltd.
>************************************************************************************
>
>
--------------020402030602030002010500
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
I ran into this as well. There are some variables in the pcb structure
that
are 8-bit or 16-bit. I changed all of these to 32-bit integers.
That seemed
to clear things up. Here is what Paul suggested when I was having this
problem:
(from the "Re: [lwip] lwip (current): large data transfers seem to break
lwip" thread)<br>
<blockquote type="cite">
<pre wrap="">to find this bug is laborious, but straight forward
do the following:
create a loooong printf statement that dumps the
state of the tcp pcb structure at every packet.
you should print the decimal/hex value of every
structure member
dump the whole thing to a log file, and see
what happens just before the stack dies
most probably, there is a tell-tail sign like
a wrapping parameter
i have found a bug this way before, but it may
not be the same bug.
you can also see what members i have changed to
be 32-bit at paulos.2038bug.com
-paul</pre>
</blockquote>
<br>
-Chris<br>
<br>
<a class="moz-txt-link-abbreviated"
href="mailto:address@hidden";>address@hidden</a> (added by color.sics.se)
wrote:<br>
<blockquote type="cite"
cite="address@hidden">
<pre wrap="">We had some problems sending large data arrays but our fix was
to change the
netconn_write function argument size from u16_t to u32_t.
Tim
-----Original Message-----
From: Kevin Stokes [<a class="moz-txt-link-freetext"
href="mailto:address@hidden";>mailto:address@hidden</a>]
Sent: jeudi, 31. octobre 2002 22:56
To: <a class="moz-txt-link-abbreviated"
href="mailto:address@hidden";>address@hidden</a>
Subject: [lwip] TCP xfer halting
I'm using version 0.5.3 of LWIP running on pure DOS (ie, not a DOS box
under Windows), compiled with DJGPP.
Connections go ok, and every seems good until I start to send some large
data arrays.
After sending 4125 packets and 4193333 bytes of data, LWIP stops sending
data on that port. It does not crash, and the stats seem ok. Other ports
are still working fine.
It is just sitting there with tcp_sndbuf() always returning a value of 0
bytes, so no more data gets sent to tcp_write().
The Windows program running on the other end of the ethernet cable is
waiting for more data, and not crashed.
Two questions:
1.) Have other people experienced this with LWIP? Is there a solution or
a bug fix for it?
2.) If not, does anybody have any suggestions for where to start in
finding the problem?
I really like LWIP, and have been lurking on the mailing list for about 5
months.
Thanks very much,
-Kevin Stokes
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (<a class="moz-txt-link-freetext"
href="http://www.grisoft.com";>http://www.grisoft.com</a>).
Version: 6.0.384 / Virus Database: 216 - Release Date: 8/21/2002
[This message was sent through the lwip discussion list.]
</pre>
<pre wrap="">
<hr width="90%" size="4">
************************************************************************************
This e-mail message is intended only for the addressee(s) and contains
information which may be confidential. If you are not the intended
recipient please do not read, save, forward, disclose or copy the contents
of this e-mail. If this e-mail has been sent to you in error, please delete
this
e-mail and any copies or links to this e-mail completely and immediately
from your system. We also like to inform you that communication via e-mail
over the Internet is insecure because third parties may have the possibility
to access and manipulate e-mails.
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
The Swatch Group Ltd.
************************************************************************************
</pre>
</blockquote>
<br>
</body>
</html>
--------------020402030602030002010500--
[This message was sent through the lwip discussion list.]