all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Hangs on redisplay_internal
Date: Mon, 03 Jun 2019 14:04:51 -0700	[thread overview]
Message-ID: <874l56bcss.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <18F33AA3-9760-4E25-8DA7-4583BC8E362C@gnu.org> (Eli Zaretskii's message of "Mon, 03 Jun 2019 09:43:21 +0300")


On 06/03/19 09:43 AM, Eli Zaretskii wrote:
> On June 3, 2019 8:56:33 AM GMT+03:00, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>> I've been updating master every three or four days, and over the past
>> week (more?) feel like I've been getting a lot of inexplicable hangs.
>> They last as long as five or six seconds, but I can usually quit out
>> of
>> them. I started running with debug on quit as a matter of course, and
>> just managed to kill one of them, and got:
>> 
>> Debugger entered--Lisp error: (quit)
>>   redisplay_internal\ \(C\ function\)()
>> 
>> That's all that was in *Backtrace*.
>> 
>> I'm on Arch Linux, and haven't done anything special to the build
>> process. I know this isn't very helpful, but maybe I can track down
>> something more.
>
> Run Emacs under GDB, and when Emacs habgs, stop it with SIGTSTP, as
> explained in etc/DEBUG. Then get a more informative backtrace with the
> GDB's "bt" command. Be sure to invoke GDB from the src directory, so
> that it will also show the Lisp backtrace.

Will do. Hopefully I'll report back in a day or so with something
useful.

Thanks,
Eric



  reply	other threads:[~2019-06-03 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  5:56 Hangs on redisplay_internal Eric Abrahamsen
2019-06-03  6:43 ` Eli Zaretskii
2019-06-03 21:04   ` Eric Abrahamsen [this message]
2019-06-13 22:23   ` Eric Abrahamsen
2019-06-13 22:32 ` Kaushal Modi

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874l56bcss.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.