From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Madhu Newsgroups: gmane.emacs.bugs Subject: bug#36648: emacs signals under gdb - [Re: connecting to a lost server process Date: Fri, 19 Jul 2019 07:23:39 +0530 (IST) Message-ID: <20190719.072339.546175785955923287.enometh@meer.net> References: <8336j3zz07.fsf@gnu.org> <20190718.202821.1196946470014157934.enometh@meer.net> <838ssvwek9.fsf@gnu.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="269752"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36648@debbugs.gnu.org To: eliz@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jul 19 03:54:09 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hoI64-001842-Ko for geb-bug-gnu-emacs@m.gmane.org; Fri, 19 Jul 2019 03:54:08 +0200 Original-Received: from localhost ([::1]:41896 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hoI63-0003IB-1C for geb-bug-gnu-emacs@m.gmane.org; Thu, 18 Jul 2019 21:54:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59452) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hoI5y-00036f-VH for bug-gnu-emacs@gnu.org; Thu, 18 Jul 2019 21:54:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hoI5x-0001pl-TB for bug-gnu-emacs@gnu.org; Thu, 18 Jul 2019 21:54:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46112) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hoI5x-0001pd-Pb for bug-gnu-emacs@gnu.org; Thu, 18 Jul 2019 21:54:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hoI5x-0001q9-Nk for bug-gnu-emacs@gnu.org; Thu, 18 Jul 2019 21:54:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Madhu Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 19 Jul 2019 01:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36648 X-GNU-PR-Package: emacs Original-Received: via spool by 36648-submit@debbugs.gnu.org id=B36648.15635012337056 (code B ref 36648); Fri, 19 Jul 2019 01:54:01 +0000 Original-Received: (at 36648) by debbugs.gnu.org; 19 Jul 2019 01:53:53 +0000 Original-Received: from localhost ([127.0.0.1]:54933 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hoI5o-0001pk-KX for submit@debbugs.gnu.org; Thu, 18 Jul 2019 21:53:52 -0400 Original-Received: from smtp6.ctinetworks.com ([205.166.61.199]:41232) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hoI5m-0001pb-7W for 36648@debbugs.gnu.org; Thu, 18 Jul 2019 21:53:50 -0400 Original-Received: from localhost (unknown [117.193.17.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: enometh@meer.net) by smtp6.ctinetworks.com (Postfix) with ESMTPSA id 9B3E983EA3; Thu, 18 Jul 2019 21:53:43 -0400 (EDT) In-Reply-To: <838ssvwek9.fsf@gnu.org> X-Mailer: Mew version 6.8 on Emacs 27.0 X-ctinetworks-Information: Please contact the ISP for more information X-ctinetworks-MailScanner-ID: 9B3E983EA3.A5462 X-ctinetworks-VirusCheck: Found to be clean X-ctinetworks-Watermark: 1564365229.21324@8SePyyTiLjUTtTSzXd5mgw 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: 209.51.188.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:163359 Archived-At: * Eli Zaretskii <838ssvwek9.fsf@gnu.org> Wrote on Thu, 18 Jul 2019 18:24:54 +0300 >> Date: Thu, 18 Jul 2019 20:28:21 +0530 (IST) >> Cc: 36648@debbugs.gnu.org >> From: Madhu >> >> >From the point of view of elisp, no error should be signalled - it >> >should be caught by the condition-case. > > You called those functions directly, from outside of the Lisp machine, > so the condition-case machinery is not working. The Lisp Language specifies how conditions are to be handled. The Lisp machine can only be a virtual machine on which that lisp code runs. If the behaviour of a piece of lisp code (however it is invoked) isn't according to the lisp specification, it is a bug in the implementation. The behaviour here can be deemed to be a bug in the implementation of condition-case rather than a design-bug in condition-case. >> However there seems to be room for improvement around the "abort when >> awaiting for input behaviour" - as there are other situations within >> gdb which are not "really" error situations which unnecessarily abort >> emacs. > > There are inherent difficulties that require this behavior, sorry. I'm sure there is some way to mitigate it, though I probably will not be able to find it. >> M-x gud-gdb RET >> gdb --args emacs --arg -Q --eval '(progn (load-library "custom") (load-library "server") (setq server-name "emacs-test"))' RET >> >> => >> >> |Reading symbols from emacs... >> (gdb) show args >> Argument list to give program being debugged when it is started is "--arg -Q --eval \'\(progn \(load-library custom \) \(load-library server \) \(setq server-name emacs-test \)\)\'". > > I suggest to use "M-x gdb", not "M-x gud-gdb". The latter is an old > and semi-deprecated way of running GDB from Emacs. [Unfortunately for me gud-gdb is the only way I can use gdb under emacs. I was using M-x gdb in emacs19, but was unable to use gdb under emacs for some time when it was replaced by gdb-mi - where it seemed a superhuman adversary would rearrange my windows and impede my workflow in myraid ways - until I discovered gud-gdb] > I guess we can close this bug report? Yes please.