|
From: | Jason Rumney |
Subject: | Re: Emacs WIN32 crashes on reinitialzing of lisp process using slime |
Date: | Fri, 13 Apr 2007 10:57:18 +0100 |
User-agent: | Thunderbird 1.5.0.10 (Windows/20070221) |
Eli Zaretskii wrote:
Probably not. There doesn't seem to be any windows specific code involved anywhere in the stack.Date: Thu, 12 Apr 2007 23:40:15 +0100 From: Jason Rumney <address@hidden> Cc: Eli Zaretskii <address@hidden>, cb <address@hidden>, address@hiddenFurther investigation shows that the kill-buffer is called recursively on the same buffer in slime-net-close, due to the hooks calling slime-net-sentinel which in turn calls slime-net-close again.That means the problem is not really Windows-specific.
How come recursive kill-buffer causes r_alloc_free to be called with a NULL pointer?
I don't know. I couldn't reproduce it by setting a kill-buffer-hook that calls kill-buffer, so it must be specific to the way it is done by slime (using a process-sentinel rather than kill-buffer-hook).
[Prev in Thread] | Current Thread | [Next in Thread] |