|
From: | Paul Eggert |
Subject: | bug#22086: 25.1.50; [PATCH] Integrate the musl hybrid malloc patch for elf systems |
Date: | Mon, 21 Dec 2015 09:11:14 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
Eli Zaretskii wrote:
It shouldn't conflict, as long as memory allocated by the system malloc is freed >by the system free, and memory allocated with emalloc is freed by >efree.I don't see how this could be arranged. E.g., the environ array might be created by the startup code, and then the application could manipulate it with setenv and unsetenv. The former will use the libc malloc, the latter emalloc/efree.
If by "startup code" you mean the C library, then it's not a problem, as portable C code already cannot free environ or environ[0] or environ[1] ... (and Emacs respects this, both when run as temacs and when run as dumped). If by "startup code" you mean something else, then I'm afraid I'm not following the example.
[Prev in Thread] | Current Thread | [Next in Thread] |