GNU bug report logs - #52446
28.0.90; Infinite loop in add_row_entry

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Po Lu <luangruo <at> yahoo.com>
Subject: bug#52446: closed (Re: bug#52446: 28.0.90; Infinite loop in
 add_row_entry)
Date: Mon, 13 Dec 2021 13:37:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#52446: 28.0.90; Infinite loop in add_row_entry

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 52446 <at> debbugs.gnu.org.

-- 
52446: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52446
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 52446-done <at> debbugs.gnu.org
Subject: Re: bug#52446: 28.0.90; Infinite loop in add_row_entry
Date: Mon, 13 Dec 2021 21:35:46 +0800

Po Lu <luangruo <at> yahoo.com> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>> Now I'm confused: if row_table[i] is NULL for each i, then how did we
>> enter that loop?  Its condition checks for entry being non-NULL.
>
> The disassembly checks out, so that condition is not being mis-compiled.
> But that doesn't rule out the possibility of a miscompilation elsewhere.
>
> I will try to reproduce this under a memory checker, and with
> optimizations turned off.

It is a miscompilation of scrolling_window, which disappeared after
updating GCC.  Closing this bug, and thanks for the help.

[Message part 3 (message/rfc822, inline)]

From: Po Lu <luangruo <at> yahoo.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 28.0.90; Infinite loop in add_row_entry
Date: Sun, 12 Dec 2021 13:15:29 +0800

Emacs froze while I was scrolling through a large image with `C-n'.  The
source of the freeze was an infinite loop in this part of
`add_row_entry':

    while (entry && !row_equal_p (entry->row, row, 1))
--->  entry = entry->next;

The problem seems to be that `entry' points to the same address as
`entry->next'.

Previous Next

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