From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: End of file while generating loaddefs.el
Date: Thu, 19 Nov 2015 18:15:21 +0200 [thread overview]
Message-ID: <83lh9u7yp2.fsf@gnu.org> (raw)
In-Reply-To: <564D848D.4000301@gmx.at>
> Date: Thu, 19 Nov 2015 09:13:01 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
>
> > If you run this command under a debugger,
>
> How do I do that?
Run "make V=1" to see the full command line of the command that fails,
then start "gdb ./emacs.exe" in the src directory, and copy/paste the
offending command line into the GDB command to run Emacs, right after
the "run" part. Then wait until it segfaults.
> > what do you see in the
> > backtrace when Emacs crashes?
>
> Attaching gdb to bootstrap-emacs.exe when it crashes gives
That's too late: when a program running not under a debugger triggers
a fatal exception, Windows invokes the global exception handler, which
in this case is installed by the MinGW startup code, so you don't see
the application stack. When a program is being debugged, the debugger
gets the first opportunity to handle the exception, so it can display
much more information.
> Lisp Backtrace:
> "prin1" (0x82ee7c)
> "autoload-insert-section-header" (0x82f008)
Looks like some GC problem to me, as prin1 uses a temporary buffer to
produce its strings.
next prev parent reply other threads:[~2015-11-19 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 17:40 End of file while generating loaddefs.el Eli Zaretskii
2015-11-18 7:50 ` martin rudalics
2015-11-18 17:29 ` Eli Zaretskii
2015-11-19 8:13 ` martin rudalics
2015-11-19 16:15 ` Eli Zaretskii [this message]
2015-11-19 16:33 ` John Wiegley
2015-11-20 8:23 ` martin rudalics
2015-11-20 8:38 ` Eli Zaretskii
2015-11-20 9:46 ` David Kastrup
2015-11-20 14:50 ` Eli Zaretskii
2015-11-20 21:10 ` Eli Zaretskii
2015-11-21 8:33 ` martin rudalics
2015-11-21 8:49 ` Eli Zaretskii
2015-11-21 11:23 ` martin rudalics
2015-11-21 11:33 ` David Kastrup
2015-11-21 11:59 ` Eli Zaretskii
2015-11-21 11:57 ` Eli Zaretskii
2015-11-21 15:29 ` Juanma Barranquero
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=83lh9u7yp2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.