[Top][All Lists]

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

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

From: Iordan Neshev
Subject: [lwip-devel] [bug #27034] Invalid ASSERT in pbuf_alloc()
Date: Wed, 15 Jul 2009 14:57:46 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2009042316 Firefox/3.0.10

Follow-up Comment #2, bug #27034 (project lwip):

>Just to ensure I understand this properly: the assertion
>incorrectly fires when you try to allocate a pbuf 
>with zero length?

Yes,that's right.

> Is there any other requirement to trigger the incorrect
> assertion? 

No. (In fact only when type == PBUF_POOL, but this is obvious)

For me it happens from the PPP code, for example in ppp.c:
  headMB = pbuf_alloc(PBUF_RAW, 0, PBUF_POOL);

but I see several other places where pbuf_alloc() is called with len=0, for
ex. ip_fraq.c, raw.c...

Last time I updated lwip in my project was 2 months
ago. Now I update again before the next release and I see this ASSERT added.

I tested it with the proposed change and it's OK.
The device works as expected, nothing bad happens till now.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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