From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 14666@debbugs.gnu.org
Subject: bug#14666: 24.3.50; emacs_backtrace.txt
Date: Wed, 19 Jun 2013 20:08:50 +0300 [thread overview]
Message-ID: <83obb2ownx.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SR4Mcam=n38zj=VzXifW429QmVoaaTmd0j-T1mJdam68Q@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 19 Jun 2013 18:48:38 +0200
> Cc: 14666@debbugs.gnu.org
>
> On Wed, Jun 19, 2013 at 6:47 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > The only explanation is that another thread modified w->contents after
> > it was tested with BUFFERP.
>
> Should that be possible?
"Should" in what sense? w32_wnd_proc, the function in which this
happens, is the main window procedure for Emacs, and it runs in the
input thread, which is separate from the Lisp thread. The code which
crashes is the only one in w32_wnd_proc that references buffers,
windows, and frames, which are objects that are manipulated (and
GC'ed) by the Lisp thread.
Did I answer your question?
next prev parent reply other threads:[~2013-06-19 17:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 15:04 bug#14666: 24.3.50; emacs_backtrace.txt Drew Adams
2013-06-19 15:14 ` Juanma Barranquero
2013-06-19 16:10 ` Eli Zaretskii
2013-06-19 16:47 ` Eli Zaretskii
2013-06-19 16:48 ` Juanma Barranquero
2013-06-19 17:08 ` Eli Zaretskii [this message]
2013-06-19 17:23 ` Juanma Barranquero
2013-06-19 17:57 ` martin rudalics
2013-06-19 18:46 ` Juanma Barranquero
2013-06-19 20:59 ` martin rudalics
2013-06-19 19:51 ` Eli Zaretskii
2013-06-19 19:44 ` Eli Zaretskii
2013-06-19 19:46 ` Juanma Barranquero
2013-06-19 20:03 ` Juanma Barranquero
2013-06-19 17:44 ` martin rudalics
2013-06-19 19:47 ` Eli Zaretskii
2013-06-19 20:58 ` martin rudalics
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=83obb2ownx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14666@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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.