[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #37148] memory pool content is being corrupted after m

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #37148] memory pool content is being corrupted after memp_free()
Date: Thu, 23 Aug 2012 09:22:26 +0000
User-agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.83 Safari/537.1

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

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

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:


  Nachricht gesendet von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]