unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, Noam Postavsky <npostavs@gmail.com>
Cc: 35784@debbugs.gnu.org, marc@bloodnok.com
Subject: bug#35784: emacs 26 crash
Date: Sat, 18 May 2019 19:30:50 +0200	[thread overview]
Message-ID: <07948e24-aeab-9ac8-9d0d-b3a704c58b08@gmx.at> (raw)
In-Reply-To: <83y33393g0.fsf@gnu.org>

 >> #2  0x000000000061849e in die (msg=0x743f3f "BUFFERP (a)",
 >> file=0x743f36 "buffer.h", line=914) at alloc.c:7406
 >> #3  0x00000000005802b3 in XBUFFER (a=0) at buffer.h:914
 >> #4  0x0000000000468bb3 in mark_window_display_accurate_1 (w=0x558e410,
 >> accurate_p=false) at xdisp.c:14754
 >>          b = 0x7ffe74b60e40
 >> #5  0x0000000000468ffd in mark_window_display_accurate
 >> (window=89711637, accurate_p=false) at xdisp.c:14811
 >>          w = 0x558e410
 >> #6  0x00000000004bbe06 in Fforce_window_update (object=89711637) at
 >> window.c:3643
 >>          w = 0x558e410
 >
 > This seems to imply that we are trying to update a non-leaf window,
 > something that should never happen.  There's no Lisp-level backtrace,
 > so it's hard to tell what Lisp called force-window-update, and how the
 > window in question became non-leaf, but maybe some crazy Lisp hook
 > switched windows behind redisplay's back or something.

I'd rather guess that this is the result of 'kill-buffer' called from
'delete-frame-functions' or 'delete-frame' called from
'kill-buffer-hook'.  But at the moment I can't reproduce the bug here
any more.

martin





  reply	other threads:[~2019-05-18 17:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 20:54 bug#35784: emacs 26 crash Marc Munro
2019-05-18  6:19 ` Eli Zaretskii
2019-05-18  9:39   ` Bhavin Gandhi
2019-05-18 12:09     ` Eli Zaretskii
2019-05-18 12:16   ` Noam Postavsky
2019-05-18 13:03     ` Eli Zaretskii
2019-05-18 14:03     ` martin rudalics
2019-05-18 14:19       ` Noam Postavsky
2019-05-18 15:39         ` Eli Zaretskii
2019-05-18 17:30           ` martin rudalics [this message]
2019-05-18 17:43             ` Eli Zaretskii
2019-05-19  2:54             ` Noam Postavsky
2019-05-19  4:51               ` Eli Zaretskii
2019-05-19  6:40                 ` martin rudalics
2019-05-19 17:11                   ` Noam Postavsky
2019-05-19 17:59                     ` Eli Zaretskii
2019-05-20 18:27                       ` Noam Postavsky
2019-05-19 23:57 ` bug#35784: Just built from head: it seems to be fixed Marc Munro

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=07948e24-aeab-9ac8-9d0d-b3a704c58b08@gmx.at \
    --to=rudalics@gmx.at \
    --cc=35784@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=marc@bloodnok.com \
    --cc=npostavs@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).