all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How much memory to debug Emacs nowadays?
Date: Fri, 01 Dec 2023 20:35:05 +0200	[thread overview]
Message-ID: <8334wlai06.fsf@gnu.org> (raw)
In-Reply-To: <87o7f9g4se.fsf@ledu-giraud.fr> (message from Manuel Giraud via Users list for the GNU Emacs text editor on Fri, 01 Dec 2023 19:24:01 +0100)

> Date: Fri, 01 Dec 2023 19:24:01 +0100
> From:  Manuel Giraud via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> 
> I was trying to debug Emacs into GDB 9.2 (through M-x gdb into another
> Emacs).  As instructed by etc/DEBUG, I have compiled it with "-O0 -g3".
> 
> But when I'm running this debugged Emacs, GDB starts to allocates *lots*
> of memory (nearly 4GB) and now I regurlarly end up with the following
> error: Recursive internal problem.
> 
> I say "now" because this used to work flawlessly some months ago.  My
> question is: Is 4GB for debugging Emacs expected or is something
> misconfigured on my side?

Something on your side, I'd say.  Just starting "emacs -Q" under GDB
takes only between 100MB and 130MB (depending on whether Emacs is
built without or with native-compilation) of memory for GDB on my
system.  (This is GDB 13.1, but I doubt that the GDB version could
matter that much.)

Does GDB allocate memory right at the beginning, or when you do
something specific in Emacs?  Also, do you invoke "emacs -Q" from GDB
or do you run Emacs with all your customizations?



  reply	other threads:[~2023-12-01 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 18:24 How much memory to debug Emacs nowadays? Manuel Giraud via Users list for the GNU Emacs text editor
2023-12-01 18:35 ` Eli Zaretskii [this message]
2023-12-01 20:01   ` Manuel Giraud via Users list for the GNU Emacs text editor

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8334wlai06.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.