From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Berman Newsgroups: gmane.emacs.bugs Subject: bug#15841: Display bugs with cache-long-lines non-nil Date: Tue, 12 Nov 2013 22:34:43 +0100 Message-ID: <87iovx718s.fsf@rosalinde.fritz.box> References: <871u2xf9st.fsf@gmail.com> <9jiow9uhoa.fsf@fencepost.gnu.org> <87wqkopylw.fsf@gmail.com> <87bo20fh3h.fsf@web.de> <834n7q95d5.fsf@gnu.org> <87r4aqww3j.fsf@nbtrap.com> <83r4aq3s4r.fsf@gnu.org> <87fvr3ni2o.fsf@rosalinde.fritz.box> <877gceo3n9.fsf@rosalinde.fritz.box> <87mwla6inw.fsf@rosalinde.fritz.box> <83txfh1t0b.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1384292114 1780 80.91.229.3 (12 Nov 2013 21:35:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Nov 2013 21:35:14 +0000 (UTC) Cc: 15841@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 12 22:35:18 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VgLcE-0005g2-5T for geb-bug-gnu-emacs@m.gmane.org; Tue, 12 Nov 2013 22:35:18 +0100 Original-Received: from localhost ([::1]:45448 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgLcD-0007KS-EH for geb-bug-gnu-emacs@m.gmane.org; Tue, 12 Nov 2013 16:35:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgLc4-0007DU-N9 for bug-gnu-emacs@gnu.org; Tue, 12 Nov 2013 16:35:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VgLby-0002VQ-Sw for bug-gnu-emacs@gnu.org; Tue, 12 Nov 2013 16:35:08 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:35233) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgLby-0002U6-NX for bug-gnu-emacs@gnu.org; Tue, 12 Nov 2013 16:35:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VgLby-0005YB-1v for bug-gnu-emacs@gnu.org; Tue, 12 Nov 2013 16:35:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Stephen Berman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 12 Nov 2013 21:35:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15841 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15841-submit@debbugs.gnu.org id=B15841.138429209521323 (code B ref 15841); Tue, 12 Nov 2013 21:35:01 +0000 Original-Received: (at 15841) by debbugs.gnu.org; 12 Nov 2013 21:34:55 +0000 Original-Received: from localhost ([127.0.0.1]:49252 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VgLbq-0005Xq-6Y for submit@debbugs.gnu.org; Tue, 12 Nov 2013 16:34:54 -0500 Original-Received: from mout.gmx.net ([212.227.15.18]:55829) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VgLbn-0005Xb-9Q for 15841@debbugs.gnu.org; Tue, 12 Nov 2013 16:34:52 -0500 Original-Received: from rosalinde.fritz.box ([89.245.100.165]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MCtut-1VouBD0CSh-009dUZ for <15841@debbugs.gnu.org>; Tue, 12 Nov 2013 22:34:44 +0100 In-Reply-To: <83txfh1t0b.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 12 Nov 2013 18:31:32 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-Provags-ID: V03:K0:xEif644bRGnk8ApXAxlIBJT87KIjgt8mKiIlJt6m0+bCWumtS+I fuNFmUDlsk3PiIi3mg2/KKJYS/BkVfUGEeAvRA4WKfKeL8FYw3wwmTkc1kSDJ9Ojq/YLgPo eXeZAVVcMAzDj+DKJt3K/DVTdjYj3LBmBDo5kGBxJeFYmSLXjMUYU9mBMwrzscHDaQW7EyO cRvHkjlbruQn+XUQq4esA== X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:80348 Archived-At: On Tue, 12 Nov 2013 18:31:32 +0200 Eli Zaretskii wrote: > I already established that, as you point out, the > changes to the buffer that cause the problem are indeed made by > decode-coding-region. The problem becomes visible when redisplay, > entered after decode-coding-region finishes its job, re-fontifies > portions of the buffer that were affected by the changes. The way > this affects redisplay is through forward-line and > line-beginning-position, of which JIT Font Lock is a heavy user. > That's why you only see the effect after decode-coding-region returns. Thanks for the explanation. >> Is it possible to have execution halt when cache_long_scans is >> checked, and if so, how? > > Watchpoints are the answer. But in this case, there's only one place > in the whole Emacs where this variable is consulted: in search.c, > around line 610, so you could just put a breakpoint there. > > In any case, I already traced through the code that is involved, and > the immediate reason for the assertion violation is that the cache > isn't being updated wrt changes in buffer size (which are caused by > decoding the stuff brought in by 'ls'). However, a naive attempt to > force such updates didn't solve the whole problem: the aborts are > gone, but the infloop is still there, and also other minor display > issues. So I guess there's another factor at work there... Fascinating, what unsuspected and apparently unrelated effects can be brought to the surface by toggling the value of a variable! > I also need to figure out how to keep the cache up to date without > penalizing performance, which would render the cache worthless. > >> Or is there a better way to try to track down this bug? > > The cache has only 3 public interfaces (see region-cache.c), so it is > easy to put breakpoints in all of them and see what happens. That's > what I did. Thanks for the advice and for working on this bug. Steve Berman