From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 23369@debbugs.gnu.org, fredrik@fornwall.net
Subject: bug#23369: 25.0.93; CANNOT_DUMP build fails if resizing terminal during startup in tty mode
Date: Wed, 27 Apr 2016 20:20:00 +0300 [thread overview]
Message-ID: <83wpnjx933.fsf@gnu.org> (raw)
In-Reply-To: <po1t5rhuum.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 27 Apr 2016 12:36:33 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: fredrik@fornwall.net, 23369@debbugs.gnu.org
> Date: Wed, 27 Apr 2016 12:36:33 -0400
>
> It's ugly to (essentially) modify all uses of save-selected-window just
> because of one (?) problematic use in an edge case. I wonder if we can
> find and fix whatever code is calling it in this case. Presumably
> something window-related that happens during resizing.
I'd still like to see a full backtrace when the problem happens, both
C and Lisp level.
> Also, it seems like if CANNOT_DUMP builds encounter an error loading
> loadup.el, they go on to run the command-loop with only a partially
> loaded loadup, which leads to confusing error messages that have nothing
> to do with the real problem. Can they be made to abort instead?
How will aborting help diagnosing the problems? IME, it tends to hide
evidence, not make it more clear.
next prev parent reply other threads:[~2016-04-27 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 7:10 bug#23369: 25.0.93; CANNOT_DUMP build fails if resizing terminal during startup in tty mode Fredrik Fornwall
2016-04-25 7:54 ` Eli Zaretskii
2016-04-25 9:43 ` Fredrik Fornwall
2016-04-25 10:01 ` Eli Zaretskii
2016-04-27 0:53 ` Glenn Morris
2016-04-27 6:52 ` Eli Zaretskii
2016-04-27 16:36 ` Glenn Morris
2016-04-27 17:20 ` Eli Zaretskii [this message]
2016-04-27 18:48 ` Glenn Morris
2016-04-27 19:27 ` Eli Zaretskii
2016-04-27 21:01 ` Glenn Morris
2016-04-28 5:28 ` Eli Zaretskii
2016-04-28 13:03 ` Fredrik Fornwall
2016-04-28 13:14 ` Eli Zaretskii
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=83wpnjx933.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23369@debbugs.gnu.org \
--cc=fredrik@fornwall.net \
--cc=rgm@gnu.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 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).