|
From: | Lennart Borgman (gmail) |
Subject: | Re: 23.0.60; Crash in face_at_buffer_position |
Date: | Tue, 15 Apr 2008 19:43:25 +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 |
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.
[Prev in Thread] | Current Thread | [Next in Thread] |