From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Any way of dumping strings? Date: Wed, 02 Jun 2021 15:30:34 -0400 Message-ID: References: <87zgw8b3n9.fsf@telefonica.net> <87mts8aygk.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6689"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: =?windows-1252?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 02 21:32:41 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 1loWbZ-0001Zg-Db for ged-emacs-devel@m.gmane-mx.org; Wed, 02 Jun 2021 21:32:41 +0200 Original-Received: from localhost ([::1]:38044 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1loWbX-0003ZW-Fz for ged-emacs-devel@m.gmane-mx.org; Wed, 02 Jun 2021 15:32:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38812) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1loWZr-0002A7-FZ for emacs-devel@gnu.org; Wed, 02 Jun 2021 15:30:55 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:41569) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1loWZp-00053k-GH for emacs-devel@gnu.org; Wed, 02 Jun 2021 15:30:54 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1ED7B80625; Wed, 2 Jun 2021 15:30:52 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 54ACD80497; Wed, 2 Jun 2021 15:30:35 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1622662235; bh=lpPgI1FPpVCgZxJAv93C/otNmQtm98ugfUj278K8GXQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=LmvcRJC8S4vmbJ+mJ2MxSBNHNgtAp4BhRY2SFDlWJ8oNphmq8gEvQESYopD5cdllS nI9U6ssxrGQSIWB8N8MmSLq1hNcYHKkS3h0oCf8F3nZzzAGcTLX87ez4ScS6v2JhLa Bby2qAWbQmdOpHyVY5+uqmb+0jpv2HZ+Z26ZuOjFPBjvkLj6V21qcixGQU40waY2+s MAAcm5FwSsJpkYEeN0dVeodJfrpIQHJeR0VFYD9rr1h6M+jm5heoNzhcfTL+yNKqVx lvWn1V9CtnC09wBzxzsjHGEJi2F06xVJz6bIuc6/g4ZkX1oFwxrJNgzugv4f72cDCZ K4teIw1xFpeNw== Original-Received: from alfajor (69-196-163-239.dsl.teksavvy.com [69.196.163.239]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 25CD6120050; Wed, 2 Jun 2021 15:30:35 -0400 (EDT) In-Reply-To: <87mts8aygk.fsf@telefonica.net> (=?windows-1252?Q?=22=D3scar?= Fuentes"'s message of "Wed, 02 Jun 2021 20:55:07 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:270327 Archived-At: =D3scar Fuentes [2021-06-02 20:55:07] wrote: > Stefan Monnier writes: >> Have you tried the new `memory-report` function? > Yes, I mention that on the message you just quoted :-) Duh! So, IIUC the report about the size of specific variables doesn't point give any hint about where those many strings&vectors are located? Too bad. I hope once you find the origin of the problem we can refine `memory-report` so that it gives info which would have been helpful now. Stefan