From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Any way of dumping strings? Date: Wed, 02 Jun 2021 21:44:22 +0300 Message-ID: <83bl8oxg1l.fsf@gnu.org> References: <87zgw8b3n9.fsf@telefonica.net> <83fsy0xjrd.fsf@gnu.org> <87v96wb19v.fsf@telefonica.net> <83czt4xhc7.fsf@gnu.org> <87r1hkazgt.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7911"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 02 20:46:05 2021 Return-path: 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 ) id 1loVsQ-0001me-S0 for ged-emacs-devel@m.gmane-mx.org; Wed, 02 Jun 2021 20:46:02 +0200 Original-Received: from localhost ([::1]:45784 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1loVsP-00020i-5p for ged-emacs-devel@m.gmane-mx.org; Wed, 02 Jun 2021 14:46:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59140) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1loVr3-0001C5-L3 for emacs-devel@gnu.org; Wed, 02 Jun 2021 14:44:37 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60092) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1loVr2-0000xb-PX; Wed, 02 Jun 2021 14:44:36 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4963 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1loVr2-0006KJ-4Y; Wed, 02 Jun 2021 14:44:36 -0400 In-Reply-To: <87r1hkazgt.fsf@telefonica.net> (message from =?utf-8?Q?=C3=93scar?= Fuentes on Wed, 02 Jun 2021 20:33:22 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:270322 Archived-At: > From: Óscar Fuentes > Date: Wed, 02 Jun 2021 20:33:22 +0200 > > > That's not what I had in mind. You can set up breakpoint commands > > that dump the contents of the vector being marked, then continue > > without stopping. Then say "set logging on", so that the output goes > > to a file, and let Emacs run. Once GC finishes, you will have a file > > with all the vectors in it; then you can examine them at your leisure. > > That looks quite useful for this purpose, thanks. > > Now that I think of it, my impression on the past session was that > performance degraded quite a bit, which could indicate that a very large > number of objects was live (which implies that the leaked objects are > relatively small, right?). I don't know. Maybe you have a significant number of medium-size objects as well. In any case, a large Lisp object in most cases also means a lot of small ones -- these are the elements of that large object: a list or a large vector or similar. Only elements that are atoms, like integers, don't add to GC's complexity, and such elements are relatively rare in Emacs.