I caught one case where i wasn't returning ERR_OK in the receive callback which
lead to the pbuf being set to refused and my callback was called again with a
already freed pbuf from the 250ms timer. But I still see the assert on really
high traffic from e.g. an intense scan by nmap.. there i got
Are you sure you are not freeing an already freed pbuf ? That is what
the assert is supposed to catch.
Try to trace back from the assert.
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Thanks Simon!
I've gone through my project and resolved some issues and the /pbc->next
! pcb /hasn't appeared anymore. In the process i also updated to lwip 2.0.2.
But i've got another issue now.. My device is listening to port 502 and
as soon as someone connects and it starts receiving package
Markus Pischinger wrote:
/LWIP_ASSERT("tcp_input: pcb->next != pcb (before cache)", pcb->next
!= pcb);
/
Normally, this is a strong indication that you are violating lwIP's
threading requirements. Read http://www.nongnu.org/lwip/2_0_x/pitfalls.html
Simon
Hello,
in one of my applications I sometimes run into the following assert:
/LWIP_ASSERT("tcp_input: pcb->next != pcb (before cache)", pcb->next
!= pcb);
/
I've already researched a bit and couldn't find the problem.. i've
checked for tcp_abort without returning ERR_ABRT and double cal
