bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#24616: 26.0.50; No backtrace when emacsclient --eval fails


From: Eli Zaretskii
Subject: bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
Date: Wed, 05 Oct 2016 09:41:08 +0300

> From: Noam Postavsky <address@hidden>
> Date: Tue, 4 Oct 2016 19:50:23 -0400
> Cc: address@hidden
> 
> >>> $ emacsclient --eval '(progn (defun f () (error "foo")) (setq 
> >>> debug-on-error t) (f))'
> >>> *ERROR*: foo
> >>>
> >>> Note that there's no backtrace. This makes it almost impossible to debug
> >>> problems when using emacsclient.
> >>>
> >>
> >> Just a note: you can get a backtrace by setting debug-on-signal
> >> instead of debug-on-error.
> >
> > Really?
> >
> > $ emacsclient --eval '(progn (defun f () (error "foo")) (setq 
> > debug-on-signal t debug-on-error t) (f))'
> > *ERROR*: foo
> >
> > Am I missing something obvious?
> 
> The backtrace shows up in Emacs, where the server is running.

How about adding this to debugging.texi?





reply via email to

[Prev in Thread] Current Thread [Next in Thread]