Debugging errors in bytecomp code?

Debugging errors in bytecomp code?

[Vibhav Pant]

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.

-- 
Vibhav Pant
vibhavp@gmail.com

Re: Debugging errors in bytecomp code?

[Stefan Monnier]

> 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) ?


        Stefan

Re: Debugging errors in bytecomp code?

[Vibhav Pant]

ah, thanks.

On Tue, Jan 31, 2017 at 8:02 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> 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) ?
>
>
>         Stefan
>
>



-- 
Vibhav Pant
vibhavp@gmail.com

Re: Debugging errors in bytecomp code?

[Philipp Stephani]

[-- 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

Re: Debugging errors in bytecomp code?

[Eli Zaretskii]

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Tue, 31 Jan 2017 18:07:05 +0000
> 
>  (setq byte-compiler-debug t) ?
> 
> While there, here's a patch to document this variable:

Thanks, please also document it in the ELisp manual, and push both
changes to emacs-25.

Re: Debugging errors in bytecomp code?

[Philipp Stephani]

[-- Attachment #1: Type: text/plain, Size: 373 bytes --]

Eli Zaretskii <eliz@gnu.org> schrieb am Di., 31. Jan. 2017 um 19:55 Uhr:

> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Tue, 31 Jan 2017 18:07:05 +0000
> >
> >  (setq byte-compiler-debug t) ?
> >
> > While there, here's a patch to document this variable:
>
> Thanks, please also document it in the ELisp manual, and push both
> changes to emacs-25.
>

Done.

[-- Attachment #2: Type: text/html, Size: 932 bytes --]