> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 22 Nov 2015 16:27:19 +0000
> Cc: eggert@cs.ucla.edu, aurelien.aptel+emacs@gmail.com, tzz@lifelogs.com,
>       emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> schrieb am So., 22. Nov. 2015 um 17:23 Uhr:
>
>     I don't understand: we already have in emacs-module.c machinery that
>     handles non-local exits. Why cannot xmalloc do the same when it's
>     called from emacs-module.c?
>
> My impression was that Paul talked about code in modules, not code in
> emacs-module.c. The latter can use xmalloc just fine, if appropriate protection
> is installed first.

I'll let Paul explain what he was worried about.  What I was worried
about is that memory allocation done by emacs-module.c on behalf of
modules doesn't behave like xmalloc does, doesn't comply to the
MALLOC_BLOCK_INPUT protocol, and cannot be probed by MALLOC_PROBE.  I
think this should be easy to fix.