From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Debugging errors in bytecomp code?
Date: Tue, 31 Jan 2017 18:07:05 +0000 [thread overview]
Message-ID: <CAArVCkS11j=FhP=4gBgEYG8eXoUOZiXsQT6+ZCbvHYTG_zjaYQ@mail.gmail.com> (raw)
In-Reply-To: <jwvvasvfggh.fsf-monnier+gmane.emacs.devel@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 447 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> schrieb am Di., 31. Jan. 2017 um
15:36 Uhr:
> > Is there a way to enter the debugger when a error in bytecomp code
> > itself is encountered? Right now, all errors including compilation ones
> > are printed to the *Compile-Log* buffer, making it impossible to get
> > a backtrace for internal compiler errors.
>
> (setq byte-compiler-debug t) ?
>
>
While there, here's a patch to document this variable:
[-- Attachment #1.2: Type: text/html, Size: 901 bytes --]
[-- Attachment #2: 0001-Document-variable-byte-compile-debug.txt --]
[-- Type: text/plain, Size: 1019 bytes --]
From 4d81eb450ef5219b551e01e7df7f08784fdc3231 Mon Sep 17 00:00:00 2001
From: Philipp Stephani <phst@google.com>
Date: Tue, 31 Jan 2017 19:04:36 +0100
Subject: [PATCH] Document variable `byte-compile-debug'
* lisp/emacs-lisp/bytecomp.el (byte-compile-debug): Document variable.
---
lisp/emacs-lisp/bytecomp.el | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
index eb3f46d3d7..2c808a5b4b 100644
--- a/lisp/emacs-lisp/bytecomp.el
+++ b/lisp/emacs-lisp/bytecomp.el
@@ -411,7 +411,8 @@ byte-compile-call-tree-sort
:type '(choice (const name) (const callers) (const calls)
(const calls+callers) (const nil)))
-(defvar byte-compile-debug nil)
+(defvar byte-compile-debug nil
+ "If non-nil, byte compile errors will be raised as signals instead of logged.")
(defvar byte-compile-constants nil
"List of all constants encountered during compilation of this form.")
(defvar byte-compile-variables nil
--
2.11.0.483.g087da7b7c-goog
next prev parent reply other threads:[~2017-01-31 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 18:06 Debugging errors in bytecomp code? Vibhav Pant
2017-01-31 14:32 ` Stefan Monnier
2017-01-31 16:50 ` Vibhav Pant
2017-01-31 18:07 ` Philipp Stephani [this message]
2017-01-31 18:54 ` Eli Zaretskii
2017-01-31 20:11 ` Philipp Stephani
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='CAArVCkS11j=FhP=4gBgEYG8eXoUOZiXsQT6+ZCbvHYTG_zjaYQ@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.