unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 19:10:26 +0300	[thread overview]
Message-ID: <83sj0eozd9.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRJa-fs1Z9yoZfQOFXYrP2nNiL5P1FYr4FacAcQsBwD0g@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 19 Jun 2013 17:14:43 +0200
> Cc: 14666@debbugs.gnu.org
> 
> 0x011ecbac: w32_backtrace at w32fns.c:7741
> 0x011ecc1e: emacs_abort at w32fns.c:7773
> 0x010d9fe0: terminate_due_to_signal at emacs.c:350
> 0x01151719: die at alloc.c:6520
> 0x01147b6b: XBUFFER at lisp.h:820
> 0x011e3ac1: w32_wnd_proc at w32fns.c:3189

I don't get it: it crashes here:

  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?





  reply	other threads:[~2013-06-19 16:10 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83sj0eozd9.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).