From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: Any way of dumping strings?
Date: Thu, 03 Jun 2021 09:08:59 +0300 [thread overview]
Message-ID: <83a6o7xyx0.fsf@gnu.org> (raw)
In-Reply-To: <jwvtumg9ib8.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 02 Jun 2021 15:30:34 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Wed, 02 Jun 2021 15:30:34 -0400
>
> Óscar Fuentes [2021-06-02 20:55:07] wrote:
> > Stefan Monnier <monnier@iro.umontreal.ca> 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.
I think a useful extension of memory-report would be optionally to
dump all live objects of a given type to somewhere. The challenge of
doing that in Lisp is that doing so will generally cons more Lisp
objects, thus skewing both the memory report and possibly the dumped
objects as well. Patches welcome.
prev parent reply other threads:[~2021-06-03 6:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 17:03 Any way of dumping strings? Óscar Fuentes
2021-06-02 17:24 ` Eli Zaretskii
2021-06-02 17:54 ` Óscar Fuentes
2021-06-02 18:16 ` Eli Zaretskii
2021-06-02 18:33 ` Óscar Fuentes
2021-06-02 18:44 ` Eli Zaretskii
2021-06-02 18:38 ` Stefan Monnier
2021-06-02 18:55 ` Óscar Fuentes
2021-06-02 19:30 ` Stefan Monnier
2021-06-03 6:08 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6o7xyx0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ofv@wanadoo.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).