|
From: | Martine Lenders |
Subject: | [lwip-devel] [bug #47334] 6LoWPAN crashes on reassembly of high payload lengths |
Date: | Sat, 05 Mar 2016 13:41:09 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36 |
Follow-up Comment #15, bug #47334 (project lwip): > What I don't understand is what does MEM_SIZE have to do with it? RX pbufs should be allocated as PBUF_POOL, which has nothing to do with MEM_SIZE. Could it be that you allocate RX pbufs as PBUF_RAM and allocate them much bigger than the 127 bytes required for 6lowpan? All I do to the packet buffer is allocating a received packet as PBUF_POOL (of exactly the length it is, which can't go over 125 (excluding FCS) for a IEEE 802.15.4 radio): https://github.com/RIOT-OS/RIOT/pull/3551/files#diff-6629cafbf0fc4d482ccec31da7bb62bdR200 anything doesn't use lwIP's packet buffer (sizeof(_tmp_buf) is 127 in my applications context btw). Where else is the data stored if not in the memory (which size is determined by MEM_SIZE). What's the stuff in mem for then if not for allocating stuff like packets? _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?47334> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |