GNU bug report logs - #24616
26.0.50; No backtrace when emacsclient --eval fails

Previous Next

Full log

View this message in rfc822 format

From: Clément Pit--Claudel <clement.pit <at> gmail.com>
To: 24616 <at> debbugs.gnu.org
Subject: bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
Date: Tue, 4 Oct 2016 18:28:07 -0400

[Message part 1 (text/plain, inline)]

On 2016-10-04 16:52, Noam Postavsky wrote:
> On Tue, Oct 4, 2016 at 12:30 PM, Philipp Stephani <p.stephani2 <at> gmail.com> 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?

Cheers,
Clément.

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.