|
From: | Paul Eggert |
Subject: | Re: Dynamic modules: emacs-module.c and signaling errors |
Date: | Wed, 25 Nov 2015 09:34:05 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 |
On 11/25/2015 09:30 AM, Eli Zaretskii wrote:
Maybe I misunderstand the issue, but AFAICS any Lisp data that is allocated by emacs-module.c on behalf of modules already goes through xmalloc, so what exactly are the remaining problems?
I think Daniel is worried that module code will call xmalloc, and then do more work that signals an Elisp error or throws a C++ exception, and the module will then leak the xmalloced memory. There may be other concerns like that too, but I'm not sure what they are.
[Prev in Thread] | Current Thread | [Next in Thread] |