unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Any way of dumping strings?
Date: Wed, 02 Jun 2021 21:44:22 +0300	[thread overview]
Message-ID: <83bl8oxg1l.fsf@gnu.org> (raw)
In-Reply-To: <87r1hkazgt.fsf@telefonica.net> (message from Óscar Fuentes on Wed, 02 Jun 2021 20:33:22 +0200)

> From: Óscar Fuentes <ofv@wanadoo.es>
> 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.



  reply	other threads:[~2021-06-02 18:44 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 [this message]
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

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=83bl8oxg1l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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).