Re: [lwip-users] LWIP_ASSERT

[Martin Velek]

Hi,

from wiki http://en.wikipedia.org/wiki/Assertion_%28software_development%29:
In computer programming, an assertion is a predicate (a true–false statement) placed in a program to indicate that the developer thinks that the predicate is always true at that place. If an assertion evaluates to false at run-time, an assertion failure results, which typically causes execution to abort.

You should restart the stack. If you are doing everything correctly, it could mean that there is a severe bug inside the lwip. Try to upgrade to 1.4.1, try to trace the situation which modifies the variables in the assertion and double check your code, e.g. using one socket in different threads, calling netif functions without the netifapi prefix, etc.

Martin

On Tue, Feb 11, 2014 at 8:08 PM, Jonathan dumaresq <address@hidden> wrote:

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

---

Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection Antivirus avast! est active.

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users