From: Richard Stallman <rms@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 46384@debbugs.gnu.org
Subject: bug#46384: 28.0.50; 100% cpu in line_number_display_width
Date: Tue, 09 Feb 2021 01:11:46 -0500 [thread overview]
Message-ID: <E1l9MFW-0000jF-Du@fencepost.gnu.org> (raw)
In-Reply-To: <m1ft26k1x3.fsf@gmail.com> (message from Aaron Jensen on Mon, 08 Feb 2021 09:35:36 -0600)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
The way I debugged infloops in Emacs was to use the GDB return command
on each frame till control got out of that frame. Eventually I would
find a frame that never returned to its caller. I would then arrange
to stop the program while inside that frame's function and find the
range of code contained in the loop.
Then I would figure out where the code was supposed to exit that loop.
After that, it is a matter of debugging why it does not exit.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-02-09 6:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 15:35 bug#46384: 28.0.50; 100% cpu in line_number_display_width Aaron Jensen
2021-02-09 6:11 ` Richard Stallman [this message]
2021-02-09 7:18 ` Eli Zaretskii
2021-02-10 5:28 ` Richard Stallman
2021-02-10 11:16 ` Eli Zaretskii
2021-02-11 13:37 ` Richard Stallman
2021-02-10 14:12 ` Robert Pluim
2021-02-10 16:06 ` Aaron Jensen
2021-02-10 16:18 ` Aaron Jensen
2021-02-10 17:54 ` Robert Pluim
2021-02-11 13:37 ` Richard Stallman
2022-06-16 13:33 ` Lars Ingebrigtsen
2022-06-16 22:40 ` Aaron Jensen
2022-06-17 12:02 ` Lars Ingebrigtsen
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=E1l9MFW-0000jF-Du@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=46384@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
/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.