unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joe Riel <joer@san.rr.com>
To: Stefan Monnier via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Emacs locks up
Date: Sun, 20 Jun 2021 09:05:20 -0700	[thread overview]
Message-ID: <20210620090520.530857e9@gauss> (raw)
In-Reply-To: <jwvwnqo3bf1.fsf-monnier+emacs@gnu.org>

On Sun, 20 Jun 2021 09:40:27 -0400
Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:

> Joe Riel [2021-06-19 14:15:22] wrote:
> > I've written a debugger controlled by Emacs.  It uses make-network-process
> > to communicate with a client over TCP.  Works fine on linux and Windows.
> > However, when running the client in Windows 10 in virtualbox, with Emacs
> > running on the host system (linux), occasionally Emacs locks up.
> >
> > When that occurs I have to kill Emacs---it is otherwise unresponsive.  
> > Have no good idea how to fix or debug this.  Just being able to restore Emacs 
> > without killing it would be useful.  Any suggestions are appreciated.  
> 
> You might like to try `kill -USR2` which may(!) bring Emacs back to life
> and give you a Lisp backtrace of where it's stuck.
> If that doesn't work, you'll need to attach to the process with
> a debugger to get the C level backtrace.

Thanks,

`kill -SIGUSR2` did restore emacs, which will be a big help.



-- 
Joe Riel




  reply	other threads:[~2021-06-20 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 21:15 Emacs locks up Joe Riel
2021-06-20  6:49 ` Eli Zaretskii
2021-06-20 13:40 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-20 16:05   ` Joe Riel [this message]
2021-06-20 16:11     ` Emanuel Berg via Users list for the GNU Emacs text editor

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=20210620090520.530857e9@gauss \
    --to=joer@san.rr.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
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).