Hi,
Le 2014-02-14 08:43, Marco Jakobs a écrit :
Hi Jonathan,
i've had the same issue and have made a bug report. There is a work
around which is works good for me, it may be worth for you checking this:
http://savannah.nongnu.org/bugs/?38219
yeah.. this was exactly the same problem. Using this patch seem to
correct the Assert.
Thanx for your help.
Jonathan
BR
Marco
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of
*Jonathan dumaresq
*Sent:* Tuesday, February 11, 2014 8:08 PM
*To:* users
*Subject:* [lwip-users] LWIP_ASSERT
Hi all,
We are working on a problem right now. I use lwip 1.4.0.
I have an LWIP_ASSERT("already writing or closing",
msg->conn->current_msg == NULL &&
msg->conn->write_offset == 0);
I think this happen when I have many pbuf ready to be sent, and I
loose the initernet. On the first send timeout, I try to close the
socket.
My question is what I sould do on LWIP_ASSERT ?
Should I just put some warning on my display and continue, or I should
stop something in the Lwip stack and reinitialise something ?
regards
Jonathan
------------------------------------------------------------------------
<http://www.avast.com/>
Ce courrier électronique ne contient aucun virus ou logiciel
malveillant parce que la protection Antivirus avast!
<http://www.avast.com/> est active.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce
que la protection avast! Antivirus est active.
http://www.avast.com
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
