This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/12140] mallopt(M_PERTURB) free() anomaly
- From: "mtk.manpages at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Wed, 17 Oct 2012 12:55:27 +0000
- Subject: [Bug malloc/12140] mallopt(M_PERTURB) free() anomaly
- Auto-submitted: auto-generated
- References: <bug-12140-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12140
--- Comment #5 from Michael Kerrisk <mtk.manpages at gmail dot com> 2012-10-17 12:55:27 UTC ---
(In reply to comment #4)
> This is tricky because it conflicts with the design of malloc. The
> user-visible memory area is used by fd and bk pointers to make the internal
> free list. I don't think there is a good way to fix this. The best I can do
> is add a note in the documentation about it.
This isn't correct. I am not talking about the bytes that re used by the fd/bk
pointers. This concerns what happens to the bytes in the usable malloc()ed
area. Please look more closely at the test program.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.