GNU bug report logs - #46384
28.0.50; 100% cpu in line_number_display_width

Previous Next

Full log

Message #11 received at 46384 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org, Richard Stallman <rms <at> gnu.org>,
 Aaron Jensen <aaronjensen <at> gmail.com>
Cc: 46384 <at> debbugs.gnu.org
Subject: Re: bug#46384: 28.0.50; 100% cpu in line_number_display_width
Date: Tue, 09 Feb 2021 09:18:36 +0200

On February 9, 2021 8:11:46 AM GMT+02:00, Richard Stallman <rms <at> gnu.org> wrote:
> 
> 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.

That procedure is described in etc/DEBUG.  However, the main problem in this case is that GDB is not easily available, so displaying Lisp objects and data structures is tedious at best.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.