From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: emacs --daemon and M-x malloc-info
Date: Mon, 26 Apr 2021 14:48:13 +0300
Message-ID: <83sg3djmgy.fsf@gnu.org>
References: <m3r1ixby4w.fsf@leonis4.robolove.meer.net>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="18081"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: emacs-devel@gnu.org
To: Madhu <enometh@meer.net>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Apr 26 13:50:19 2021
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1lazkm-0004T7-TM
	for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Apr 2021 13:50:16 +0200
Original-Received: from localhost ([::1]:56318 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1lazkm-0001gw-0Q
	for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Apr 2021 07:50:16 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40132)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1lazjK-0000TI-Va
 for emacs-devel@gnu.org; Mon, 26 Apr 2021 07:48:48 -0400
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53665)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>)
 id 1lazjK-000719-CG; Mon, 26 Apr 2021 07:48:46 -0400
Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2633
 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>)
 id 1lazj4-0001Te-Kx; Mon, 26 Apr 2021 07:48:43 -0400
In-Reply-To: <m3r1ixby4w.fsf@leonis4.robolove.meer.net> (message from Madhu on
 Mon, 26 Apr 2021 07:33:27 +0530)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: "Emacs-devel"
 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Xref: news.gmane.io gmane.emacs.devel:268456
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/268456>

> From: Madhu <enometh@meer.net>
> Date: Mon, 26 Apr 2021 07:33:27 +0530
> 
> Fmalloc_info writes to stderr, which is closed in a daemonized emacs.

AFAIU, this happens only in the background daemon.  So using a
foreground daemon should allow you to redirect the output to a file.

> A new logfile argument to emacs

I don't see a reason to add a new knob, when there is already a
solution.  This is a diagnostic feature, so even if the daemon didn't
have a solution at all, I would hesitate adding a new option: you can
always run Emacs normally, and any serious memory related problem will
show itself in that configuration as well.