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

[Simon Goldschmidt]

Update of bug #37148 (project lwip):

                  Status:            Works For Me => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #5:

> Ok. It was just suggestion because you asked "Why is pool content
overwritten?"

I asked that because I didn't understand what was overwritten. By "memory pool
content is being corrupted" I thought you meant the pool's linked list got
corrupted.

Changing MEMP_SIZE *should* work for what you want to do. I won't say it's
correct, though - it may or may not work with future changes to memp.c.

Relying on memory to remain untouched while unallocated is not a very portable
thing to do anyway, I guess. What you're doing seems like a tradeoff of SRAM
size (increased memp pools) for code size (not having to implement the
list-keeping of unallocated system items yourself).

I'll close this as invalid now.

    _______________________________________________________

Reply to this item at:

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

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