all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: lekktu@gmail.com
Cc: 14666@debbugs.gnu.org
Subject: bug#14666: 24.3.50; emacs_backtrace.txt
Date: Wed, 19 Jun 2013 19:47:23 +0300	[thread overview]
Message-ID: <83ppvioxno.fsf@gnu.org> (raw)
In-Reply-To: <83sj0eozd9.fsf@gnu.org>

> Date: Wed, 19 Jun 2013 19:10:26 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 14666@debbugs.gnu.org
> 
>   LISP_INLINE struct buffer *
>   XBUFFER (Lisp_Object a)
>   {
>     eassert (BUFFERP (a));
>     return XUNTAG (a, Lisp_Vectorlike);  <<<<<<<<<<<<<<<
>   }
> 
> I don't see how XUNTAG can crash, so the only possible cause that's
> left is the assertion before that.  But how can the assertion be
> false, when line 3189 of w32fns.c is only executed if w->contents _is_
> a buffer?

The only explanation is that another thread modified w->contents after
it was tested with BUFFERP.





  reply	other threads:[~2013-06-19 16:47 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 [this message]
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
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=83ppvioxno.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.