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

[Jonathan Larmour]

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

Maybe it might be worth tweaking mem.h to be something like:
#if MEM_LIBC_MALLOC
/* aliases for C library malloc() */
#ifndef mem_init
# define mem_init()
#endif
#ifndef mem_free
# define mem_free(x) free(x)
#endif
#ifndef mem_malloc
# define mem_malloc(x) malloc(x)
#endif
#ifndef mem_realloc
# define mem_realloc(x, size) realloc(x,size)
#endif

This way a port can choose to provide its own function, even if it's only a
wrapper around malloc, adding some locking.

What do you think?

To answer the other part of the initial report: yes there are systems with
string functions but not a heap implementation.


    _______________________________________________________

Reply to this item at:

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

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