[uClibc]malloc ?

Marshall M. Midden m4 at brecis.com
Mon Jun 17 17:38:53 UTC 2002


I was wondering if it is just me, or ...
(uclibc code grabbed from snapshot april 22nd)

I am using a "mips" port of uClibc, without mmu, and therefore
with my own set of system calls, etc.

If I use "MALLOC = malloc", then programs that run forever
and do malloc/free will keep grabbing more and more memory.

Yet, "MALLOC = malloc-simple" works just fine.
(Some simple tests work fine ... which makes it more difficult
to figure out where the problem might be.)
(Note: uClibc-0.9.9 and 0.9.10 have same behavior)

Is this something I should track down?

[Why?  If I put in "bash" as "sh", 167 malloc's are done,
and having that many system calls to mmap is quite a bit of
overhead.  Doing that many "copies" to make fork work upon
process context switches is not desirable.]

Any ideas or suggestions?



More information about the uClibc mailing list