From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri,  7 Nov 2014 23:30:26 +0300
From: Oleg <lego12239@yandex.ru>
To: 9fans@9fans.net
Message-ID: <20141107203026.GC1825@localhost>
References: <20141106210544.GA20298@localhost>
	<CAOw7k5jWi-ViqbouHziixGP7QegGDSc5zC+OU8zvxV98PKWBQQ@mail.gmail.com>
	<20141107094425.GA29497@localhost>
	<20141107105708.cOSXGRv3%sdaoden@yandex.com>
	<CAOw7k5iGCvOeaaLFy99UC+5JMLTSq9T4Cj0D=3p5S-QQfnmyAQ@mail.gmail.com>
	<20141107121929.GA10144@localhost>
	<CAOw7k5hsiLD1pXUwVu3M4XYoqhCRqKnTDKLdH_Q7jVbtX+aNnw@mail.gmail.com>
	<1ee0d370c013b1efefe0000738299d50@ladd.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1ee0d370c013b1efefe0000738299d50@ladd.quanstro.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [9fans] atexit() & atexitdont()
Topicbox-Message-UUID: 254c52be-ead9-11e9-9d60-3106f5b1d025

On Fri, Nov 07, 2014 at 02:53:11PM -0500, erik quanstrom wrote:
> On Fri Nov  7 07:26:55 EST 2014, charles.forsyth@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?