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: Debug wedged Emacs Date: Wed, 13 Dec 2017 05:46:12 +0200 Message-ID: <83po7juw6z.fsf@gnu.org> References: <63939C6E-4338-454E-B075-6E621DD3134C@jovi.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1513136825 28665 195.159.176.226 (13 Dec 2017 03:47:05 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 13 Dec 2017 03:47:05 +0000 (UTC) Cc: Emacs-Devel@gnu.org To: Devon Sean McCullough Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 13 04:46:59 2017 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 1eOy0Y-00076n-Tv for ged-emacs-devel@m.gmane.org; Wed, 13 Dec 2017 04:46:59 +0100 Original-Received: from localhost ([::1]:33414 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOy0g-0007n5-7H for ged-emacs-devel@m.gmane.org; Tue, 12 Dec 2017 22:47:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40933) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOxzz-0007my-Kw for Emacs-Devel@gnu.org; Tue, 12 Dec 2017 22:46:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eOxzw-000513-JG for Emacs-Devel@gnu.org; Tue, 12 Dec 2017 22:46:23 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59451) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOxzw-00050z-FZ; Tue, 12 Dec 2017 22:46:20 -0500 Original-Received: from [176.228.60.248] (port=2201 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eOxzv-0003W0-SR; Tue, 12 Dec 2017 22:46:20 -0500 In-reply-to: <63939C6E-4338-454E-B075-6E621DD3134C@jovi.net> (message from Devon Sean McCullough on Tue, 12 Dec 2017 17:30:06 -0500) 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:220984 Archived-At: > From: Devon Sean McCullough > Date: Tue, 12 Dec 2017 17:30:06 -0500 > > Emacs 26.0.90 unresponsive, 100% CPU, I would like to find the name and contents of the current buffer. > > (lldb) version > lldb-310.2.37 > (lldb) bt > ### The backtrace seems to show a sit-for leading to an infinite fontify loop or something. Please show the backtrace, it's hard to reason about the problem without having that much. > (lldb) expression --gdb-format x -- (long)Fcurrent_buffer() > (long) $24 = 0x000000010a499125 > … > (lldb) expression --gdb-format x --show-types -- (long)Fbuffer_name((long)Fcurrent_buffer()) > (long) $30 = 0x000000010a58e9b4 > … > (lldb) expression --gdb-format x --show-types -- (long)VALMASK > (long) $40 = 0xfffffffffffffff8 > … > (lldb) expression --gdb-format x --show-types -- (long)GCTYPEBITS > (long) $44 = 0x0000000100000003 > … > (lldb) expression --gdb-format x --show-types -- (long)Fbuffer_name((long)Fcurrent_buffer()) & (long)VALMASK > (long) $45 = 0x000000010a58e9b0 > … > (lldb) memory read --gdb-format xb --count 64 0x000000010A58E9B0 > 0x10a58e9b0: 0x0d 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > 0x10a58e9b8: 0x0d 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > 0x10a58e9c0: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > 0x10a58e9c8: 0xe0 0x16 0x30 0x51 0x01 0x00 0x00 0x00 > 0x10a58e9d0: 0x5c 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > 0x10a58e9d8: 0x5c 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > 0x10a58e9e0: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > 0x10a58e9e8: 0x40 0xb3 0xc1 0x4f 0x01 0x00 0x00 0x00 > > Now what? Can lldb use the commands defined in src/.gdbinit? If so, you should be able to display the name of the current buffer in a human-readable form using "xbuffer", for example.