From: storm@cua.dk (Kim F. Storm)
To: martin rudalics <rudalics@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>,
carstenblaauw@web.de, emacs-devel@gnu.org,
Jason Rumney <jasonr@gnu.org>
Subject: Re: Emacs WIN32 crashes on reinitialzing of lisp process using slime
Date: Fri, 13 Apr 2007 14:20:19 +0200 [thread overview]
Message-ID: <m3odlssby4.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <461F6F60.4010007@gmx.at> (martin rudalics's message of "Fri\, 13 Apr 2007 13\:54\:08 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> 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).
>
> kill-buffer has a window of opportunity before it sets buffer-name to
> nil. Could you try reproducing the slime crash with the patch I sent to
> emacs-pretest?
Could you also try if the following (simpler) patch gives good results.
*** buffer.c 29 Mar 2007 22:06:47 +0200 1.525
--- buffer.c 13 Apr 2007 14:17:29 +0200
***************
*** 1458,1464 ****
--- 1458,1470 ----
unlock_buffer (b);
#endif /* CLASH_DETECTION */
+ GCPRO1 (buf);
kill_buffer_processes (buf);
+ UNGCPRO;
+
+ if (NILP (b->name))
+ return Qnil;
+
clear_charpos_cache (b);
tem = Vinhibit_quit;
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2007-04-13 12:20 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
2007-04-13 11:54 ` martin rudalics
2007-04-13 12:20 ` Kim F. Storm [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3odlssby4.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=carstenblaauw@web.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=rudalics@gmx.at \
/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.