Re: 23.0.60; Crash in face_at_buffer_position

["Lennart Borgman (gmail)" <lennart.borgman@gmail.com>]

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.