From: Michael Heerdegen <michael_heerdegen@web.de>
To: Jude DaShiell <jdashiel@panix.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: .emacs warning
Date: Wed, 12 Jul 2017 20:10:54 +0200 [thread overview]
Message-ID: <878tjty18x.fsf@drachen> (raw)
In-Reply-To: <alpine.NEB.2.20.1707121358190.14609@panix1.panix.com> (Jude DaShiell's message of "Wed, 12 Jul 2017 13:58:46 -0400 (EDT)")
Jude DaShiell <jdashiel@panix.com> writes:
> How do I generate a back trace and save it in a file?
First, it's better to load the (uncompiled) .el sources of related files
if you have them so that the backtrace doesn't contain only nearly
unreadable byte code.
You need to turn on debug-on-error, e.g. with M-x set-option.
Then reproduce the problem (error). The debugger should pop up. You
can use C-x C-w from within the debugger buffer to save the contents to
a file as usual.
Michael.
prev parent reply other threads:[~2017-07-12 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 4:26 .emacs warning Jude DaShiell
2017-07-12 17:52 ` Michael Heerdegen
2017-07-12 17:58 ` Jude DaShiell
2017-07-12 18:10 ` Michael Heerdegen [this message]
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=878tjty18x.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=jdashiel@panix.com \
/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.
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).