From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14666@debbugs.gnu.org
Subject: bug#14666: 24.3.50; emacs_backtrace.txt
Date: Wed, 19 Jun 2013 19:23:12 +0200 [thread overview]
Message-ID: <CAAeL0SSRRuwoSW081uoKGhEWqzvXngGZcDA4WejcRa-p-y-RXw@mail.gmail.com> (raw)
In-Reply-To: <83obb2ownx.fsf@gnu.org>
On Wed, Jun 19, 2013 at 7:08 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> "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.
I was afraid you'd say something like that :-)
> Did I answer your question?
More or less. It is obvious that using these macros in a place where
their assumptions can be violated is a no-no (as witnessed by this
crash).
Still, shouldn't that happen much more frequently? Or it is
WM_IME_STARTCOMPOSITION infrecuent? (I would've guessed it would
mostly show up in localized version of Windows, BTW...)
J
next prev parent reply other threads:[~2013-06-19 17:23 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
2013-06-19 17:23 ` Juanma Barranquero [this message]
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=CAAeL0SSRRuwoSW081uoKGhEWqzvXngGZcDA4WejcRa-p-y-RXw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=14666@debbugs.gnu.org \
--cc=eliz@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 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.