On Fri, Nov 07, 2014 at 02:53:11PM -0500, erik quanstrom wrote: > On Fri Nov 7 07:26:55 EST 2014, charles.fors...@gmail.com wrote: > > > Not for atexit, but for some other functions, I've had to follow various > > trails in glibc, > > and it's just an intricate convoluted nightmare, so that probably colours > > my view. > > calling malloc from the atexit path will pull malloc() into every executable. > i think this is the real reason not to do this.
That's interesting. Is malloc() so huge to worry about it?
