From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs locked when internet connection is cut... [+ help-gnu-emacs: Invalid read syntax: ")" ] Date: Tue, 08 May 2018 05:32:20 +0300 Message-ID: <83sh72q3m3.fsf@gnu.org> References: <83r2mvqvaq.fsf@gnu.org> <4260C366-2B75-4501-BD7A-7D224C9C50A7@gmail.com> <83a7tbqr2k.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1525746621 14094 195.159.176.226 (8 May 2018 02:30:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 8 May 2018 02:30:21 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 08 04:30:17 2018 Return-path: Envelope-to: ged-emacs-devel@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 1fFsON-0003X0-1C for ged-emacs-devel@m.gmane.org; Tue, 08 May 2018 04:30:15 +0200 Original-Received: from localhost ([::1]:49070 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fFsQU-0001jc-4l for ged-emacs-devel@m.gmane.org; Mon, 07 May 2018 22:32:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43077) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fFsQN-0001jW-Oe for emacs-devel@gnu.org; Mon, 07 May 2018 22:32:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fFsQI-0004jX-PO for emacs-devel@gnu.org; Mon, 07 May 2018 22:32:19 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:36889) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fFsQI-0004jP-ME; Mon, 07 May 2018 22:32:14 -0400 Original-Received: from [176.228.60.248] (port=3764 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fFsQI-0003e5-4F; Mon, 07 May 2018 22:32:14 -0400 In-reply-to: (message from Jean-Christophe Helary on Tue, 8 May 2018 09:43:56 +0900) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:225145 Archived-At: > From: Jean-Christophe Helary > Date: Tue, 8 May 2018 09:43:56 +0900 > > Put a breakpoint in Fsignal, and when it reports this error, show the backtrace. > > When I check the emacs manual, the only reference to Fsignal is: > > "To make Lisp errors stop Emacs and return to GDB, put a breakpoint at Fsignal." > > Also, there is no reference to Fsignal in the GDB manual. $ cd /path/to/emacs/src $ gdb ./emacs ... (gdb) break Fsignal (gdb) commands > pp errror_symbol > end (gdb) run Thread 1 hit Breakpoint 3, Fsignal (error_symbol=XIL(0x108b0), data=XIL(0xc000000001976940)) at eval.c:1514 1514 signal_or_quit (error_symbol, data, false); void-variable (gdb) continue Keep typing "continue" until error_symbol is invalid_syntax. Then: (gdb) bt OK?