From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri,  7 Nov 2014 14:53:11 -0500
To: 9fans@9fans.net
Message-ID: <1ee0d370c013b1efefe0000738299d50@ladd.quanstro.net>
In-Reply-To: <CAOw7k5hsiLD1pXUwVu3M4XYoqhCRqKnTDKLdH_Q7jVbtX+aNnw@mail.gmail.com>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] atexit() & atexitdont()
Topicbox-Message-UUID: 2540f5ea-ead9-11e9-9d60-3106f5b1d025

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.

- erik