[lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes

[David van Moolenbroek]

Follow-up Comment #1, bug #50040 (project lwip):

FWIW, I can indeed reproduce this problem. I believe that the root cause here
is that "mem_size_t" is being defined to u16_t for some configurations. Due to
integer promotion the addition itself will not cause an overflow, but the
result does get coerced into mem_size_t in the resulting mem_malloc() call.
When I force-change mem_size_t to u32_t here, things "work" as expected, in
that lwIP crashes on an assertion that I don't have any pools that are
sufficiently large for the allocation request.

I'm afraid this is one of several issues in the area of close-to-maximum pbuf
sizes. Patch #9209 solves another such issue.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?50040>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/