[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lwip-devel] [bug #27034] Invalid ASSERT in pbuf_alloc()

From: Bill Auerbach
Subject: RE: [lwip-devel] [bug #27034] Invalid ASSERT in pbuf_alloc()
Date: Wed, 15 Jul 2009 14:19:41 -0400

>However, I'd like to know what the purpose of
>  pbuf_alloc(PBUF_RAW, 0, PBUF_POOL);
>is? Since there is no API that supports increasing a pbuf's length
>moving the payload to the front (which you can't in this case, because
>PBUF_RAW is used), you'll end up with a pbuf of zero length, which is
>bound to
>lead to problems in other parts of the stack. There are checks for pbuf-
>not being zero somewhere... (although I don't remember where and why).

The above is used in PPP, and I use:

pbuf_alloc( PBUF_RAW, 0, PBUF_REF )

in my application.  It's useful for zero-copy output operations.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]