BTW, how can I check the number o pbufs, total/available for debug report? This may be a very important information to detect problems beforehand!!!
thanks, Alain Em 25-09-2014 09:04, Becker Markus escreveu:
Hi, we've had a pbuf leak of the PBUF_POOL when using the httpserver_raw from lwip-contrib.git at the processing of HTTP POSTs, which led to the complete stack becoming unresponsive. Our fix was in http_post_request(struct pbuf **inp, struct http_state *hs, char *data, u16_t data_len, char *uri, char *uri_end) to add pbuf_free(*inp); just before just before line 1479 *inp = NULL; So that the incoming packet is actually freed, which I think Can this be confirmed by others? Is anyone else using the HTTP POST code path of lwip? In order to reduce the time to failure we've set PBUF_POOL_SIZE to a low value. BR, Markus ________________________________________________________ The contents of this e-mail and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this e-mail is received in error, please immediately notify the sender and delete the e-mail and attached documents. Please note that neither the sender nor the sender's company accept any responsibility for viruses and it is your responsibility to scan or otherwise check this e-mail and any attachments. _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users