From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Thu, 19 Nov 2015 08:37:53 -0800 Organization: UCLA Computer Science Department Message-ID: <564DFAE1.4010406@cs.ucla.edu> References: <877flswse5.fsf@lifelogs.com> <8737wgw7kf.fsf@lifelogs.com> <87io5bv1it.fsf@lifelogs.com> <87egfzuwca.fsf@lifelogs.com> <876118u6f2.fsf@lifelogs.com> <8737w3qero.fsf@lifelogs.com> <831tbn9g9j.fsf@gnu.org> <878u5upw7o.fsf@lifelogs.com> <83ziya8xph.fsf@gnu.org> <83y4du80xo.fsf@gnu.org> <564DF0F6.5060501@cs.ucla.edu> <83k2pe7y44.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1447951104 12462 80.91.229.3 (19 Nov 2015 16:38:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Nov 2015 16:38:24 +0000 (UTC) Cc: aurelien.aptel+emacs@gmail.com, tzz@lifelogs.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 19 17:38:08 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZzSDo-0004ll-5n for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2015 17:38:08 +0100 Original-Received: from localhost ([::1]:42839 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzSDn-00014W-FJ for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2015 11:38:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56375) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzSDj-00014F-SS for emacs-devel@gnu.org; Thu, 19 Nov 2015 11:38:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzSDi-0006Nl-Uw for emacs-devel@gnu.org; Thu, 19 Nov 2015 11:38:03 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:44101) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzSDd-0006NK-7e; Thu, 19 Nov 2015 11:37:57 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id D559E160DFA; Thu, 19 Nov 2015 08:37:54 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Ts4spLORJ_DC; Thu, 19 Nov 2015 08:37:54 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 32506160DFC; Thu, 19 Nov 2015 08:37:54 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id iHWluqzHhday; Thu, 19 Nov 2015 08:37:54 -0800 (PST) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 18BA6160DFA; Thu, 19 Nov 2015 08:37:54 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 In-Reply-To: <83k2pe7y44.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194800 Archived-At: On 11/19/2015 08:27 AM, Eli Zaretskii wrote: > The code in module.c runs in Emacs, so I think it's friendly enough > (apart of the xmalloc issue). Or did I misunderstand what you meant? It's the xmalloc issue. That is, if a module contains random C code inside a library outside of your control that invokes malloc, I suppose it's a lost cause, we can't memory-profile that. But if as part of a module you write a wrapper for Emacs, the wrapper code should use xmalloc rather than malloc, so that at least we can account for its memory and fail in a standard way if it's not available. That sort of thing.