From: Eli Zaretskii <eliz@gnu.org>
To: Devon Sean McCullough <Emacs-Hacker2017@jovi.net>
Cc: Emacs-Devel@gnu.org
Subject: Re: Debug wedged Emacs
Date: Wed, 13 Dec 2017 05:46:12 +0200 [thread overview]
Message-ID: <83po7juw6z.fsf@gnu.org> (raw)
In-Reply-To: <63939C6E-4338-454E-B075-6E621DD3134C@jovi.net> (message from Devon Sean McCullough on Tue, 12 Dec 2017 17:30:06 -0500)
> From: Devon Sean McCullough <Emacs-Hacker2017@jovi.net>
> 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.
prev parent reply other threads:[~2017-12-13 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 22:30 Debug wedged Emacs Devon Sean McCullough
2017-12-13 3:46 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83po7juw6z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Emacs-Devel@gnu.org \
--cc=Emacs-Hacker2017@jovi.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).