From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; Crash in face_at_buffer_position Date: Tue, 15 Apr 2008 20:33:09 +0200 Message-ID: <4804F4E5.8070104@gmail.com> References: <480362A7.4010403@gmail.com> <480378C7.5050904@gmail.com> <87tzi3e01s.fsf@stupidchicken.com> <4804E93D.3090406@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1208284713 24560 80.91.229.12 (15 Apr 2008 18:38:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 15 Apr 2008 18:38:33 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, Stefan Monnier To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 15 20:39:03 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Jlpyp-0005oL-6v for ged-emacs-devel@m.gmane.org; Tue, 15 Apr 2008 20:34:07 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JlpyA-0000ss-Rm for ged-emacs-devel@m.gmane.org; Tue, 15 Apr 2008 14:33:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jlpy5-0000qD-GH for emacs-devel@gnu.org; Tue, 15 Apr 2008 14:33:21 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jlpy3-0000nN-Ov for emacs-devel@gnu.org; Tue, 15 Apr 2008 14:33:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jlpy3-0000n0-H6 for emacs-devel@gnu.org; Tue, 15 Apr 2008 14:33:19 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jlpy3-0000gn-46 for emacs-devel@gnu.org; Tue, 15 Apr 2008 14:33:19 -0400 Original-Received: from mx10.gnu.org ([199.232.76.166]) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1Jlpy2-0007D3-PZ for emacs-pretest-bug@gnu.org; Tue, 15 Apr 2008 14:33:18 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Jlpxx-0000fh-NS for emacs-pretest-bug@gnu.org; Tue, 15 Apr 2008 14:33:18 -0400 Original-Received: from ch-smtp01.sth.basefarm.net ([80.76.149.212]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jlpxx-0000fC-3Z for emacs-pretest-bug@gnu.org; Tue, 15 Apr 2008 14:33:13 -0400 Original-Received: from c83-254-150-27.bredband.comhem.se ([83.254.150.27]:63923 helo=[127.0.0.1]) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Jlpxv-0008SJ-50; Tue, 15 Apr 2008 20:33:11 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: <4804E93D.3090406@gmail.com> X-Antivirus: avast! (VPS 080415-1, 2008-04-15), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.150.27 X-Scan-Result: No virus found in message 1Jlpxv-0008SJ-50. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1Jlpxv-0008SJ-50 237a1d53ab0a490fcf06070ee39953f8 X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:95304 gmane.emacs.pretest.bugs:22036 Archived-At: Lennart Borgman (gmail) wrote: > Chong Yidong wrote: >>>> Most likely the SIGSEGV is nothing more than stack-overflow because of >>>> "infinite" recursion and the bug is probably not in >>>> face_at_buffer_position. >>> But how can I see where it is? The parameters to >>> face_at_buffer_position looks strange. Maybe that is something useful? >> >> It might be that the code in xdisp.c could be rewritten to avoid the >> risk of buffer overflow. Could you send a reproducible crash recipe, if >> possible? > > I am sorry. Somehow I have lost it when fighting this. > > Before that I saw however that the source of the problem was a bit > different from what I originally thought. I had (in a rather despetate > move) put a > > (font-lock -1) > > in the error handling part of a condition-case in one of my > fontification functions. That seems to be the immediate source. > > At the moment it beats me why I can't reproduce it. I just tested adding > (font-lock-mode -1) again, but the looping just continues this time. Eh, and now I know how to reproduce that crash. I just have to make certain that (font-lock-mode -1) is executed too. I have no simple example though. Would it ok if I upload a zip file to my server containing this and some other (unrelated) things and give some very simple instructions? That is the quickest way for me and I think it is easy for you too.