From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#28176: 26.0.50; Emacs hangs on entering a specific article in gnus Date: Wed, 23 Aug 2017 21:21:04 +0300 Message-ID: <83wp5u87sf.fsf@gnu.org> References: <83lgmcc2i8.fsf@gnu.org> <83d17obyyc.fsf@gnu.org> <838ticbv5p.fsf@gnu.org> <83tw0zabb9.fsf@gnu.org> <83k21va05e.fsf@gnu.org> <83fucj9fyg.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1503512538 21084 195.159.176.226 (23 Aug 2017 18:22:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 23 Aug 2017 18:22:18 +0000 (UTC) Cc: 28176@debbugs.gnu.org To: sds@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Aug 23 20:22:11 2017 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 1dkaI3-0004xt-H8 for geb-bug-gnu-emacs@m.gmane.org; Wed, 23 Aug 2017 20:22:07 +0200 Original-Received: from localhost ([::1]:45167 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dkaI9-0006v5-TP for geb-bug-gnu-emacs@m.gmane.org; Wed, 23 Aug 2017 14:22:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46910) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dkaI2-0006tp-FE for bug-gnu-emacs@gnu.org; Wed, 23 Aug 2017 14:22:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dkaHy-0005Bk-Ay for bug-gnu-emacs@gnu.org; Wed, 23 Aug 2017 14:22:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:42999) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dkaHy-0005Bg-75 for bug-gnu-emacs@gnu.org; Wed, 23 Aug 2017 14:22:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dkaHy-00019g-0j for bug-gnu-emacs@gnu.org; Wed, 23 Aug 2017 14:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 23 Aug 2017 18:22:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28176 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28176-submit@debbugs.gnu.org id=B28176.15035125004415 (code B ref 28176); Wed, 23 Aug 2017 18:22:01 +0000 Original-Received: (at 28176) by debbugs.gnu.org; 23 Aug 2017 18:21:40 +0000 Original-Received: from localhost ([127.0.0.1]:51680 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dkaHc-000199-Dt for submit@debbugs.gnu.org; Wed, 23 Aug 2017 14:21:40 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:55810) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dkaHa-00018x-Sa for 28176@debbugs.gnu.org; Wed, 23 Aug 2017 14:21:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dkaHU-0004ry-Ml for 28176@debbugs.gnu.org; Wed, 23 Aug 2017 14:21:33 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53201) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dkaHO-0004ma-RP; Wed, 23 Aug 2017 14:21:26 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3771 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dkaHM-0004HN-BX; Wed, 23 Aug 2017 14:21:26 -0400 In-reply-to: (message from Sam Steingold on Wed, 23 Aug 2017 13:03:12 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:136114 Archived-At: > From: Sam Steingold > Cc: 28176@debbugs.gnu.org > Date: Wed, 23 Aug 2017 13:03:12 -0400 > > > * Eli Zaretskii [2017-08-23 05:27:03 +0300]: > > > > if you succeed to hit a breakpoint in Fsignal and we then succeed to > > understand which code signals an error and what error, we may be on > > our way to solve the problem. > > I set the breakpoints using > > --8<---------------cut here---------------start------------->8--- > (lldb) break set -b Fsignal > Breakpoint 1: where = emacs`Fsignal + 4 at eval.c:1505, address = 0x00000001001370a4 > (lldb) break set -b xsignal > Breakpoint 2: where = emacs`xsignal + 4 at lisp.h:3829, address = 0x00000001000b5f54 > (lldb) run -Q > --8<---------------cut here---------------end--------------->8--- > > and got several hits (in require) before I even got the *Scratch* frame. > Then I got a gazillion hits on M-x gnus, so I disabled the breakpoint > and re-enabled it after viewing several articles but before viewing the > bad one (so that everything autoloaded would be loaded before the > error). > > here is the backtrace: Thanks, but this doesn't look like the error we are looking for: it doesn't happen in redisplay. To make more sense of this error, you need to convert error_symbol and data to human-readable form. If lldb doesn't support the scripting in the .gdbinit file, then the only way is to perform manually what the following commands do: xsymbol (for error_symbol) xtype (for data) After we know what is the Lisp type of data, we need to use the corresponding x* commands to display that type, like xcar and xcdr for a cons cell. > note that require is _still_ present, but it is probably the actual > suspect - feature 237581408. Why is that suspect? > I have no idea what to do next. After we understand this error, and my guess that it is not what we are looking for is confirmed, the next step is continue the program and wait for the next time the breakpoint in Fsignal breaks. Thanks.