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

[Simon Goldschmidt]

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

When using MEM_LIBC_MALLOC, at least on some platforms, there will be a
multithreading problem since malloc() is by default not protected. Is this a
problem? Should we have a semaphore around the calls to malloc/free/realloc
as we have it in our normal mem_malloc() implementation?

Apart from that, why do we have our own mem_malloc() if we by default include
<string.h> in many files? Are there toolchains including the
'string.h'-functions which lack the 'stdlib.h'-functions?

    _______________________________________________________

Reply to this item at:

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

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