[lwip-devel] [bug #37148] memory pool content is being corrupted after memp_free()

[Simon Goldschmidt]

Update of bug #37148 (project lwip):

                  Status:                    None => Works For Me           
             Assigned to:                    None => goldsimon              

    _______________________________________________________

Follow-up Comment #1:

Could you go a little more into detail here, please? Why is pool content
overwritten? The only thing we do here is to reuse the 'next' pointer: when an
allocated item is not in the pool, we don't need the next pointer.

>From your last line, my guess is that you are trying to use the memp pools in
a wrong way, i.e. initialize objects and put them back into the pool by
calling memp_free(xxx, obj) and expecting for obj to remain its state when
reallocated by memp_malloc() later. This is invalid: the memp-pools don't hold
objects, they only hold memory, the contents of which is *not* kept between
memp_free() and memp_malloc().

> Did anybody tried to implement it before me?

Regarding your statement "preallocate system objects": yes, but in the correct
way :-)

    _______________________________________________________

Reply to this item at:

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

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