Eli Zaretskii <
address@hidden> schrieb am So., 22. Nov. 2015 um 17:56 Uhr:
> From: Philipp Stephani <address@hidden>
> Date: Sun, 22 Nov 2015 16:27:19 +0000
> Cc: address@hidden, address@hidden, address@hidden,
> address@hidden
>
> Eli Zaretskii <address@hidden> 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.
Yes, I've attached a patch.
0001-Use-xmalloc-in-module-code.patch