[lwip-devel] [bug #17922] mem_malloc bug

[Simon Goldschmidt]

Follow-up Comment #16, bug #17922 (project lwip):

>However i didn't enable it since it seem to break TCP, but maybe that is
because it assumes some behavior of the broken mem_malloc(). I did not have
the time to trace that issue.

What exactly did you see to say it broke TCP? TCP should not depend on
mem_malloc() implementation (other than getting memory :)

I noticed though that your patch did some funny things because first you set
mem->next to mem2 and then mem2->next to mem->next. I'll investigate if that
is the problem...

>No idea. Didn't look at the stats, and yes it seems wrong too.
I saw it was already that way in the first version checked into svannah
CVS... Maybe noone ever really cared, but I think I'll change that, too.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/