From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: carstenblaauw@web.de, emacs-devel@gnu.org
Subject: Re: Emacs WIN32 crashes on reinitialzing of lisp process using slime
Date: Fri, 13 Apr 2007 10:57:18 +0100 [thread overview]
Message-ID: <461F53FE.9000800@gnu.org> (raw)
In-Reply-To: <uirc0k43d.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Thu, 12 Apr 2007 23:40:15 +0100
>> From: Jason Rumney <jasonr@gnu.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, cb <carstenblaauw@web.de>,
>> emacs-devel@gnu.org
>>
>> Further 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.
>
Probably not. There doesn't seem to be any windows specific code
involved anywhere in the stack.
> 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).
next prev parent reply other threads:[~2007-04-13 9:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 19:01 Emacs WIN32 crashes on reinitialzing of lisp process using slime cb
2007-04-12 3:09 ` Eli Zaretskii
2007-04-12 5:31 ` cb
2007-04-12 19:11 ` Eli Zaretskii
2007-04-12 22:13 ` Jason Rumney
2007-04-12 22:40 ` Jason Rumney
2007-04-13 9:37 ` Eli Zaretskii
2007-04-13 9:57 ` Jason Rumney [this message]
2007-04-13 11:54 ` martin rudalics
2007-04-13 12:20 ` Kim F. Storm
2007-04-13 12:37 ` Jason Rumney
2007-04-13 12:52 ` Kim F. Storm
2007-04-13 18:38 ` Eli Zaretskii
2007-04-13 23:01 ` Kim F. Storm
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=461F53FE.9000800@gnu.org \
--to=jasonr@gnu.org \
--cc=carstenblaauw@web.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).