From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: lekktu@gmail.com, 14666@debbugs.gnu.org
Subject: bug#14666: 24.3.50; emacs_backtrace.txt
Date: Wed, 19 Jun 2013 22:51:49 +0300 [thread overview]
Message-ID: <83k3lpq3oq.fsf@gnu.org> (raw)
In-Reply-To: <51C1F101.80806@gmx.at>
> Date: Wed, 19 Jun 2013 19:57:21 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: Eli Zaretskii <eliz@gnu.org>, 14666@debbugs.gnu.org
>
> > 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).
>
> I don't think that macros are important here. They simply obscure the
> backtrace.
Not only that. They also evaluate the same expressions several times,
assuming that the same expression always evaluates to the same value.
> If the input thread wants to calculate a window's size and the Lisp
> thread deletes the window under its feet, we're lost anyway.
I don't think we are lost in this particular case, see the
documentation of ImmSetCompositionWindow function that is being called
here.
next prev parent reply other threads:[~2013-06-19 19:51 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
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 [this message]
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=83k3lpq3oq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14666@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--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.