unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: End of file while generating loaddefs.el
Date: Fri, 20 Nov 2015 16:50:27 +0200	[thread overview]
Message-ID: <83oaeo67yk.fsf@gnu.org> (raw)
In-Reply-To: <87y4dt3svk.fsf@fencepost.gnu.org>

> From: David Kastrup <dak@gnu.org>
> Cc: martin rudalics <rudalics@gmx.at>,  emacs-devel@gnu.org
> Date: Fri, 20 Nov 2015 10:46:55 +0100
> 
> You can then run
> 
> gdb src/emacs core   # or whatever your corresponding binary was
> 
> and then do a post-mortem debug, particularly looking at the backtrace.

Post-mortem debugging Emacs core files is a pain because you cannot
evaluate Lisp, so examining Lisp data is tedious at best, and
downright impractical at worst.



  reply	other threads:[~2015-11-20 14:50 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
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 [this message]
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

  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=83oaeo67yk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dak@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 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).