Re: [lwip-users] lwip 1.4.1 pcb->next != pcb assert

[Markus Pischinger]

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 this assert on 
some packets that weren't even directed to my applications port, so maybe some 
problem with the atmel gmac driver/port.. 
i can give more info on monday if needed! 

markus 

> Am 01.09.2017 um 17:51 schrieb Sergio R. Caprile <address@hidden>:
> 
> 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
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lwip-users