[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, 25 Oct 2016 21:46:40 -0400 |
On Sun, Oct 23, 2016 at 8:51 PM, Live System User <nyc4bos@aol.com> wrote:
>
> This example doesn't work for me with Emacs daemon and the default
> Emacs terminal:
>
> 0. emacs -Q --daemon
> Warning: due to a long standing Gtk+ bug
> http://bugzilla.gnome.org/show_bug.cgi?id=85715
> Emacs might crash when run in daemon mode and the X11 connection is
> unexpectedly lost.
> Using an Emacs configured with --with-x-toolkit=lucid does not have this
> problem.
> Starting Emacs daemon.
>
> 1. emacsclient -n --eval '(progn (defun f () (error "foo")) (setq
> debug-on-signal t debug-on-error t) (f))'
>
> (Aside: Although the option "-n" was used, Emacs doesn't return to the
> command prompt.)
>
>
> 2. From another xterm, connect to the Emacs server in order to see the
> *backtrace* buffer that should have been created:
>
> emacsclient -n non-existant-file.txt
>
> You now see an Emacs in the default TTY-mode with the *backtrace* buffer
> displayed:
Hmm, I just get an empty *backtrace* buffer in that case. If I start a
tty-mode client before making the error, the backtrace pops up as
expected with no problems though.
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, (continued)
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Noam Postavsky, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Clément Pit--Claudel, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Noam Postavsky, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Clément Pit--Claudel, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/05
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, npostavs, 2016/10/22
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/22
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, npostavs, 2016/10/22
bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Live System User, 2016/10/23
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails,
Noam Postavsky <=