From: Tom Tromey <tromey@redhat.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: sds@gnu.org, emacs-devel@gnu.org
Subject: Re: threads and kill-buffer
Date: Wed, 05 Sep 2012 14:34:00 -0600 [thread overview]
Message-ID: <87bohkp5tz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87txvcs2f7.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Thu, 06 Sep 2012 04:19:24 +0900")
>>>>> "Stephen" == Stephen J Turnbull <stephen@xemacs.org> writes:
Stephen> Eg, A starts writing to the buffer, B kills it, it gets GC'd
Stephen> and reallocated, this time for byte-code running in thread C,
Stephen> and A starts playing "core wars" with what it thinks is its
Stephen> current buffer.[2]
Stephen> [2] Before the thread advocates start stoning me, let me acknowledge
Stephen> that this scenario is highly unlikely even in the worst case, and
Stephen> more or less impossible for the kinds of applications normally
Stephen> proposed for Emacs Lisp threads (eg, asynchronous I/O). But it's at
Stephen> least theoretically possible with preemptive threads and Sufficiently
Stephen> Stupid Code[tm].
No, it really is impossible in the context of Emacs, even with
preemptive threads. The impossibility lies in the "GCd and reallocated"
step. If thread A has a handle on the buffer, then it cannot be GCd.
Tom
next prev parent reply other threads:[~2012-09-05 20:34 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 20:36 threads and kill-buffer Tom Tromey
2012-09-04 20:43 ` Lars Ingebrigtsen
2012-09-04 21:03 ` Paul Eggert
2012-09-05 2:53 ` Eli Zaretskii
2012-09-05 14:20 ` Sam Steingold
2012-09-05 16:35 ` Eli Zaretskii
2012-09-05 16:50 ` Sam Steingold
2012-09-05 16:54 ` Eli Zaretskii
2012-09-05 19:19 ` Stephen J. Turnbull
2012-09-05 20:34 ` Tom Tromey [this message]
2012-09-06 0:20 ` Stephen J. Turnbull
2012-09-06 1:53 ` Tom Tromey
2012-09-06 8:34 ` Stephen J. Turnbull
2012-09-05 18:13 ` Stefan Monnier
2012-09-05 18:28 ` Tom Tromey
2012-09-05 19:14 ` Stefan Monnier
2012-09-05 18:20 ` Tom Tromey
2012-09-05 19:00 ` Stephen J. Turnbull
2012-09-05 19:10 ` Tom Tromey
2012-09-05 19:50 ` Eli Zaretskii
2012-09-05 20:48 ` Stephen J. Turnbull
2012-09-06 5:16 ` Eli Zaretskii
2012-09-06 9:22 ` Stephen J. Turnbull
2012-09-06 10:58 ` Eli Zaretskii
2012-09-07 1:26 ` Stephen J. Turnbull
2012-09-05 20:25 ` Stephen J. Turnbull
2012-09-05 19:45 ` Eli Zaretskii
2012-09-05 19:46 ` Eli Zaretskii
2012-09-06 2:28 ` Stefan Monnier
2012-09-06 5:24 ` Eli Zaretskii
2012-09-06 12:32 ` Stefan Monnier
2012-09-05 3:49 ` SAKURAI Masashi
2012-09-05 4:34 ` Dmitry Antipov
2012-09-05 9:44 ` martin rudalics
2012-09-05 16:28 ` Eli Zaretskii
2012-09-06 7:19 ` martin rudalics
2012-09-06 7:56 ` Eli Zaretskii
2012-09-06 14:41 ` martin rudalics
2012-09-06 14:55 ` Eli Zaretskii
2012-09-06 16:04 ` martin rudalics
2012-09-06 17:07 ` Stefan Monnier
2012-09-06 17:37 ` martin rudalics
2012-09-06 18:22 ` Eli Zaretskii
2012-09-06 19:25 ` Eli Zaretskii
2012-09-07 9:52 ` martin rudalics
2012-09-06 21:28 ` Stefan Monnier
2012-09-07 9:52 ` martin rudalics
2012-09-07 14:44 ` Stefan Monnier
2012-09-07 16:13 ` martin rudalics
2012-09-07 18:31 ` Stefan Monnier
2012-09-06 20:49 ` PJ Weisberg
2012-09-07 5:52 ` Eli Zaretskii
2012-09-07 15:28 ` PJ Weisberg
2012-09-08 14:58 ` Nix
2012-09-08 15:21 ` Eli Zaretskii
2012-09-08 19:45 ` Stefan Monnier
2012-09-05 13:41 ` Stefan Monnier
2012-09-05 14:34 ` Tom Tromey
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=87bohkp5tz.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=emacs-devel@gnu.org \
--cc=sds@gnu.org \
--cc=stephen@xemacs.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 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.