From: Eli Zaretskii <eliz@gnu.org>
To: Marc Munro <marc@bloodnok.com>
Cc: 29726@debbugs.gnu.org
Subject: bug#29726: 25.1; SIGSEGV in find-file
Date: Sun, 17 Dec 2017 19:23:32 +0200 [thread overview]
Message-ID: <837etlqne3.fsf@gnu.org> (raw)
In-Reply-To: <1513457838.13815.40.camel@bloodnok.com> (message from Marc Munro on Sat, 16 Dec 2017 12:57:18 -0800)
[Please keep the bug address on the CC list.]
> From: Marc Munro <marc@bloodnok.com>
> Date: Sat, 16 Dec 2017 12:57:18 -0800
>
> The code that actually brings up the new frame is called from k-
> frame::place-buffer based on the window-list it is provided with from
> k-frame::display-buffer-actor. Ultimately the code that brings up the
> frame is in k-frame::place-buffer-in-new-frame
>
> As for the backtrace buffer, yes I think you are right. In my case the
> crash occurs some time after the frame is created, but it could easily
> stem from the frame creation itself.
>
> Try making *Backtrace* a special case that k-frame::display-buffer-
> actor does nothing with, and then display-buffer will presumably bring
> up the backtrace in a suitable window.
OK, I've succeeded in reproducing the crash. The immediate reason is
clear, but I need to look a bit deeper to understand how did that
reason come into existence. Stay tuned.
(The problem with your code that caused a Lisp backtrace on my system
is that you assume the outer-window-id frame parameter is non-nil and
is always a number, but that is only true on X, and I'm on MS-Windows.
I replaced outer-window-id with window-id to work around that; maybe
you should do that as well.)
next prev parent reply other threads:[~2017-12-17 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 21:48 bug#29726: 25.1; SIGSEGV in find-file Marc Munro
2017-12-16 9:35 ` Eli Zaretskii
2017-12-16 19:43 ` Marc Munro
2017-12-16 20:07 ` Eli Zaretskii
2017-12-16 20:31 ` Marc Munro
2017-12-16 20:35 ` Marc Munro
2017-12-16 20:48 ` Eli Zaretskii
[not found] ` <1513457838.13815.40.camel@bloodnok.com>
2017-12-17 17:23 ` Eli Zaretskii [this message]
2017-12-17 19:27 ` Marc Munro
2017-12-23 12:07 ` Eli Zaretskii
2017-12-23 21:05 ` Marc Munro
2017-12-24 3:21 ` Eli Zaretskii
2017-12-16 20:44 ` Marc Munro
2017-12-16 20:56 ` Eli Zaretskii
2017-12-16 9:42 ` 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=837etlqne3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29726@debbugs.gnu.org \
--cc=marc@bloodnok.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.