all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-pretest-bug@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: 23.0.60; Crash in face_at_buffer_position
Date: Tue, 15 Apr 2008 19:43:25 +0200	[thread overview]
Message-ID: <4804E93D.3090406@gmail.com> (raw)
In-Reply-To: <87tzi3e01s.fsf@stupidchicken.com>

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.




  reply	other threads:[~2008-04-15 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 13:56 23.0.60; Crash in face_at_buffer_position Lennart Borgman (gmail)
2008-04-14 14:35 ` Stefan Monnier
2008-04-14 15:31   ` Lennart Borgman (gmail)
2008-04-15 13:10     ` Chong Yidong
2008-04-15 17:43       ` Lennart Borgman (gmail) [this message]
2008-04-15 18:33         ` Lennart Borgman (gmail)
2008-04-15 23:37           ` Chong Yidong
2008-04-20 22:27             ` Chong Yidong
2008-04-20 22:46               ` Lennart Borgman (gmail)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4804E93D.3090406@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.