From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#24616: 26.0.50; No backtrace when emacsclient --eval fails Date: Tue, 25 Oct 2016 21:46:40 -0400 Message-ID: References: <8737jmlgc8.fsf@aol.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1477446450 5600 195.159.176.226 (26 Oct 2016 01:47:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 26 Oct 2016 01:47:30 +0000 (UTC) Cc: 24616@debbugs.gnu.org, =?UTF-8?Q?Cl=C3=A9ment?= Pit--Claudel To: Live System User Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 26 03:47:26 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bzDJG-0008UO-JX for geb-bug-gnu-emacs@m.gmane.org; Wed, 26 Oct 2016 03:47:18 +0200 Original-Received: from localhost ([::1]:59054 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzDJI-000206-PU for geb-bug-gnu-emacs@m.gmane.org; Tue, 25 Oct 2016 21:47:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzDJ3-0001xy-Kk for bug-gnu-emacs@gnu.org; Tue, 25 Oct 2016 21:47:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzDJ0-0008Or-Fy for bug-gnu-emacs@gnu.org; Tue, 25 Oct 2016 21:47:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:41485) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bzDJ0-0008On-Bg for bug-gnu-emacs@gnu.org; Tue, 25 Oct 2016 21:47:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bzDJ0-0008Qt-2P for bug-gnu-emacs@gnu.org; Tue, 25 Oct 2016 21:47:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 26 Oct 2016 01:47:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24616 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 24616-submit@debbugs.gnu.org id=B24616.147744640832395 (code B ref 24616); Wed, 26 Oct 2016 01:47:02 +0000 Original-Received: (at 24616) by debbugs.gnu.org; 26 Oct 2016 01:46:48 +0000 Original-Received: from localhost ([127.0.0.1]:56884 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bzDIl-0008QR-RG for submit@debbugs.gnu.org; Tue, 25 Oct 2016 21:46:48 -0400 Original-Received: from mail-oi0-f52.google.com ([209.85.218.52]:35009) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bzDIk-0008QE-Sx for 24616@debbugs.gnu.org; Tue, 25 Oct 2016 21:46:47 -0400 Original-Received: by mail-oi0-f52.google.com with SMTP id i127so75580577oia.2 for <24616@debbugs.gnu.org>; Tue, 25 Oct 2016 18:46:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=auTfivGvTlV+SvPrl6abmjVViChGEwgI7GHeWqxYdXk=; b=s/nBPqMI0/pg/t8WTHAy7j/A1BoA7i082uUTOddj124qtif3ZP/k8kIzFRZqTJBNy3 iGHQleEzydx9McV8f9XXGKbHb//42h/u7HKW4hbvvPd22IcwrcV1D4urdpHVJHaJL994 XUch1TndY0rPTG0IKGNIWiUv4Xmmd7dcmbYSAvosg9WSEYkII4RqwNdD3q9fxs4ToNSz vg+a6RNpGfA+m/EAmBh3xk4kM6VQtoFRGQxtjzPRSQrKNRNt/BUMl5adK4nysSXHoOci Ow8ptoe1sk1dahkWIW1cmXSIFWzwBkv3GxLmpwSw2D95ChmaFioM2ABq9jgzrGrhWyIF Gkvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=auTfivGvTlV+SvPrl6abmjVViChGEwgI7GHeWqxYdXk=; b=bsx4yqQiBdBrsO+NfG4HvvwfPAifRbp/6Z34g5yHJq7oNWXILI4kCYDKxX9IZruRef f7BNsmOxOyNTL7dfxGITxCYDAE9M4XaQOE4cQrbC9W92++hepDDBB4H+Ef9NiA9HxBo+ D/YxPGSvTE9MNbsZcLdlRwhYJv/o6YQO0/2SHffjjVnAMeX2Z5tfFBWws53EM2axvYZC SCkLbnYewYgTDylcZkuAfo6kj5/oin5Ks3YftEpgPNhQ+nM/vLpCPRgMgTtLN/FJnTTp m0YFJpHl/FjA0AjtMWnmFON1pvGcnNyDdUGEPjRHKTACPBuHGgl90DILsHCUZdGBFtT3 6KwQ== X-Gm-Message-State: AA6/9RlSBLEW+SZhftuVn/pB4wtoQRQYEAfAeDOZd3sbRBnk3qy3fyD/GpIYvyhUXX4sV0J4EVc03JJ8mc58Nw== X-Received: by 10.202.83.198 with SMTP id h189mr27230586oib.89.1477446401303; Tue, 25 Oct 2016 18:46:41 -0700 (PDT) Original-Received: by 10.157.29.239 with HTTP; Tue, 25 Oct 2016 18:46:40 -0700 (PDT) In-Reply-To: <8737jmlgc8.fsf@aol.com> X-Google-Sender-Auth: g_YAGW8f6wHB0wjICC3wChUy-Ic X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:125025 Archived-At: On Sun, Oct 23, 2016 at 8:51 PM, Live System User 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.