This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] libmudflap, freebsd malloc issue
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: James E Wilson <wilson at specifix dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: 17 Aug 2005 21:42:11 -0400
- Subject: Re: [patch] libmudflap, freebsd malloc issue
- References: <1124321342.20011.76.camel@aretha.corp.specifix.com>
wilson wrote:
> [...] The program calls the malloc wrapper, which calls the real
> malloc, which calls the mmap wrapper, which calls the real malloc to
> register the data. Now we have a recursive malloc call, and that
> triggers a fatal signal inside the FreeBSD library. [...]
It's not quite clear to me how different this is from mallocs that are
entirely implemented in terms of mmap. In any case, what would just
using the "reentrant" state do in your scenario? The intention would
be to let the mmap wrapper call right to the system mmap and not
allocate tracking data.
- FChE