This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/10756] free doesn't free all memory alloced by memalign
- From: "pasky at suse dot cz" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 12 Oct 2009 06:58:07 -0000
- Subject: [Bug libc/10756] free doesn't free all memory alloced by memalign
- References: <20091011145743.10756.phil.pratt.szeliga@gmail.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From pasky at suse dot cz 2009-10-12 06:58 -------
Just to note, if it would cause your program to actually grow its memory usage
indefinitely, i.e. the freed memory wouldn't be reused in future mallopt()
calls, that would indeed be bug. But I don't see that being a case, putting a
simple while (1) loop around the mallopt()-free().
I don't think relying on functions like this to behave responsibly in such a
memory-tight environment like the SPU is reasonable. Actually, I haven't done
much SPU programming but from what I know I'm not sure if calling malloc from
the SPU context makes any sense whatsoever...
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10756
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.