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: Noam Postavsky
Subject: bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
Date: Tue, 4 Oct 2016 19:50:23 -0400

On Tue, Oct 4, 2016 at 6:28 PM, Clément Pit--Claudel
<address@hidden> wrote:
> On 2016-10-04 16:52, Noam Postavsky wrote:
>> On Tue, Oct 4, 2016 at 12:30 PM, Philipp Stephani <address@hidden> wrote:
>>>
>>> Start the server.
>>> Then run e.g.
>>>
>>> $ 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.





reply via email to

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