From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to debug high CPU usage -> hang
Date: Thu, 12 Jan 2023 11:36:38 +0100 [thread overview]
Message-ID: <874jsw82fd.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83v8lckxv8.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Jan 2023 09:36:43 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
[...]
>> Attaching a debugger to the lisp major mode, or building emacs from
>> source?
>
> Attaching a debugger (GDB) to Emacs when its CPU usage jumps. This
> requires Emacs built with debug info, or installing the separate debug
> info from your distro.
And if you get the Emacs source tree, you should read etc/DEBUG that
contains most of the informations you need to do this.
--
Manuel Giraud
prev parent reply other threads:[~2023-01-12 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 14:58 How to debug high CPU usage -> hang Ken Goldman
2023-01-10 15:21 ` Eli Zaretskii
2023-01-11 20:24 ` Ken Goldman
2023-01-12 7:36 ` Eli Zaretskii
2023-01-12 10:36 ` Manuel Giraud [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=874jsw82fd.fsf@ledu-giraud.fr \
--to=manuel@ledu-giraud.fr \
--cc=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.
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).