Re: [lwip-users] Is LWIP_SUPPORT_CUSTOM_PBUF functionality proper ?

Arpit Agarwal wrote: > But Still I am unable to figure out Why Assertion fails happen or in which > scenario it can happen. Assertions are included in the code at various places to ensure data is as expected. The "custom_free_function" pointer is stored in RAM so even if initialized it can be

Re: [lwip-users] Is LWIP_SUPPORT_CUSTOM_PBUF functionality proper ?

Hi,Can anyone help me out on this ?   Thanks, Arpit   - Original Message - Sender : Arpit Agarwal  Senior Software Engineer/SRI-Bangalore-IoTivity/Samsung Electronics Date : 2016-11-07 12:35 (GMT+5:30) Title : RE: Is LWIP_SUPPORT_CUSTOM_PBUF

Re: [lwip-users] Is LWIP_SUPPORT_CUSTOM_PBUF functionality proper ?

Hi, Sorry for the 1st query, I think typecasting is proper. But Still I am unable to figure out Why Assertion fails happen or in which scenario it can happen. Thanks, Arpit   - Original Message - Sender : Arpit Agarwal  Senior Software

[lwip-users] Is LWIP_SUPPORT_CUSTOM_PBUF functionality proper ?

  Hello All, I am facing assertion fail issue in pbuf_free API. The code where assert fails is mentioned below. if ((p->flags & PBUF_FLAG_IS_CUSTOM) != 0)  {    struct pbuf_custom *pc = (struct pbuf_custom *)p;    LWIP_ASSERT("pc->custom_free_function != NULL",