[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #17922] mem_malloc bug
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #17922] mem_malloc bug |
Date: |
Wed, 11 Apr 2007 09:51:07 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2 |
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/
- [lwip-devel] [bug #17922] mem_malloc bug,
Simon Goldschmidt <=
- [lwip-devel] [bug #17922] mem_malloc bug, Christiaan Simons, 2007/04/11
- [lwip-devel] [bug #17922] mem_malloc bug, Simon Goldschmidt, 2007/04/11
- [lwip-devel] [bug #17922] mem_malloc bug, Jonathan Larmour, 2007/04/11
- [lwip-devel] [bug #17922] mem_malloc bug, Simon Goldschmidt, 2007/04/24
- [lwip-devel] [bug #17922] mem_malloc bug, Jonathan Larmour, 2007/04/24
- [lwip-devel] [bug #17922] mem_malloc bug, Simon Goldschmidt, 2007/04/24
- [lwip-devel] [bug #17922] mem_malloc bug, Christiaan Simons, 2007/04/25
- [lwip-devel] [bug #17922] mem_malloc bug, Simon Goldschmidt, 2007/04/25
- [lwip-devel] [bug #17922] mem_malloc bug, Christiaan Simons, 2007/04/25
- [lwip-devel] [bug #17922] mem_malloc bug, Simon Goldschmidt, 2007/04/25