all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Filipp Gunbin <fgunbin@fastmail.fm>,
	andreyk.mad@gmail.com, Dmitry Gutov <dgutov@yandex.ru>
Subject: Proced signals (was: Change in vc-git ls-files-unknown makes emacs hang)
Date: Sat, 21 Dec 2019 23:51:18 +0200	[thread overview]
Message-ID: <87imm94msx.fsf_-_@mail.linkov.net> (raw)
In-Reply-To: <83fthf1mff.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Dec 2019 09:33:08 +0200")

>> So, opinions welcome.
>
> My HO is that we need to understand better which code causes the
> freeze, before we can discuss solutions.
>
> Filipp, please produce a backtrace during the freeze, either by using
> SIGUSR2, as Stefan suggested, or by attaching a debugger, and post the
> backtrace.

BTW, why proced.el doesn't support SIGUSR2?  Is this because
some standard doesn't declare SIGUSR2 as "portable"?



  parent reply	other threads:[~2019-12-21 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 14:16 Change in vc-git ls-files-unknown makes emacs hang Filipp Gunbin
2019-12-19 14:41 ` Dmitry Gutov
2019-12-19 20:44   ` Filipp Gunbin
2019-12-19 22:42     ` Dmitry Gutov
2019-12-20  7:33       ` Eli Zaretskii
2019-12-20 10:52         ` Filipp Gunbin
2019-12-20 14:13           ` Dmitry Gutov
2019-12-20 15:36             ` Filipp Gunbin
2019-12-20 15:40               ` Dmitry Gutov
2019-12-20 17:14                 ` Filipp Gunbin
2019-12-20 22:18                   ` Dmitry Gutov
2019-12-21 21:51         ` Juri Linkov [this message]
2019-12-22 17:02           ` Proced signals (was: Change in vc-git ls-files-unknown makes emacs hang) Eli Zaretskii
2019-12-19 20:45 ` Change in vc-git ls-files-unknown makes emacs hang Stefan Monnier

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=87imm94msx.fsf_-_@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=andreyk.mad@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fgunbin@fastmail.fm \
    /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.