From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: enometh@meer.net, emacs-devel@gnu.org
Subject: Re: (select-window nil) crash with gcc-8.2.0
Date: Sun, 07 Apr 2019 19:16:30 +0300 [thread overview]
Message-ID: <83y34l94f5.fsf@gnu.org> (raw)
In-Reply-To: <m2bm1ijniv.fsf@linux-m68k.org> (message from Andreas Schwab on Sun, 07 Apr 2019 09:13:44 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Sun, 07 Apr 2019 09:13:44 +0200
> Cc: emacs-devel@gnu.org
>
> On Apr 07 2019, Madhu <enometh@meer.net> wrote:
>
> > the problem is that if gcc is producing the wrong code then the
> > backtrace is unreliable. This is not the backtrace one would expect
> > from calling (select-window nil).
>
> Step through select_window to see where it goes wrong.
Right. And I'm afraid the stepping will need to be done on machine
instruction level, i.e. "stepi", not "step". The backtrace looks
completely bogus, it doesn't even show the file names correctly, let
alone line numbers.
The main issue here is why CHECK_LIVE_WINDOW doesn't do its job in
that case. It does here, and signals an error because nil is not a
live window.
next prev parent reply other threads:[~2019-04-07 16:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 2:11 (select-window nil) crash with gcc-8.2.0 Madhu
2019-04-07 3:50 ` Eli Zaretskii
2019-04-07 5:19 ` Madhu
2019-04-07 7:13 ` Andreas Schwab
2019-04-07 16:16 ` Eli Zaretskii [this message]
2019-04-07 18:33 ` Paul Eggert
2019-04-07 18:38 ` Eli Zaretskii
2019-04-07 18:42 ` Paul Eggert
2019-04-08 22:08 ` Richard Stallman
2019-04-09 4:39 ` Paul Eggert
2019-04-09 23:13 ` Richard Stallman
2019-04-10 2:01 ` Paul Eggert
2019-04-11 18:38 ` Paul Eggert
2019-05-26 6:51 ` finding the pdmp file again Madhu
2019-05-27 10:32 ` Andreas Schwab
2019-05-27 20:13 ` Richard Stallman
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=83y34l94f5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=enometh@meer.net \
--cc=schwab@linux-m68k.org \
/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.