unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Manuel Giraud via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: How much memory to debug Emacs nowadays?
Date: Fri, 01 Dec 2023 19:24:01 +0100	[thread overview]
Message-ID: <87o7f9g4se.fsf@ledu-giraud.fr> (raw)

Hi,

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?

Thanks,
-- 
Manuel Giraud



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

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

  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=87o7f9g4se.fsf@ledu-giraud.fr \
    --to=help-gnu-emacs@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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. 
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).