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 22:27:05 +0300 [thread overview]
Message-ID: <83r3dqyhrq.fsf@gnu.org> (raw)
In-Reply-To: <8mvb32ripi.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 27 Apr 2016 14:48:41 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: fredrik@fornwall.net, 23369@debbugs.gnu.org
> Date: Wed, 27 Apr 2016 14:48:41 -0400
>
> Eli Zaretskii wrote:
>
> > I'd still like to see a full backtrace when the problem happens, both
> > C and Lisp level.
>
> I can't get one. I just get "NSTATICS too small" (even if I make it huge).
If you run that command under GDB, with a breakpoint on the code which
issues this message, don't you get the backtrace?
> >> 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.
>
> In that Emacs might stop near the actual error (eg "loading foo..."),
> rather than going on to fail with some totally unrelated error (eg
> "Symbol's function definition is void: internal-echo-keystrokes-prefix"
> as in this case).
But the error message is actually quite informative; at the very
least, it tells where the problem happened, and frequently also names
the guilty function or variable.
next prev parent reply other threads:[~2016-04-27 19:27 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
2016-04-27 18:48 ` Glenn Morris
2016-04-27 19:27 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r3dqyhrq.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 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.