unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* Emacs locks up
@ 2021-06-19 21:15 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
  0 siblings, 2 replies; 5+ messages in thread
From: Joe Riel @ 2021-06-19 21:15 UTC (permalink / raw)
  To: Help GNU Emacs

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.

-- 
Joe Riel




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Emacs locks up
  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
  1 sibling, 0 replies; 5+ messages in thread
From: Eli Zaretskii @ 2021-06-20  6:49 UTC (permalink / raw)
  To: help-gnu-emacs

> Date: Sat, 19 Jun 2021 14:15:22 -0700
> From: Joe Riel <joer@san.rr.com>
> 
> 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.

First, this is hardly the proper place for discussing bugs in Emacs.
I suggest to file a bug report with all the details, and discuss this
in the thread about the bug report.

And the first thing I'd do when Emacs hangs is attach a debugger to it
and see where it hangs and possibly also why.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Emacs locks up
  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
  1 sibling, 1 reply; 5+ messages in thread
From: Stefan Monnier via Users list for the GNU Emacs text editor @ 2021-06-20 13:40 UTC (permalink / raw)
  To: help-gnu-emacs

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.


        Stefan




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Emacs locks up
  2021-06-20 13:40 ` Stefan Monnier via Users list for the GNU Emacs text editor
@ 2021-06-20 16:05   ` Joe Riel
  2021-06-20 16:11     ` Emanuel Berg via Users list for the GNU Emacs text editor
  0 siblings, 1 reply; 5+ messages in thread
From: Joe Riel @ 2021-06-20 16:05 UTC (permalink / raw)
  To: Stefan Monnier via Users list for the GNU Emacs text editor
  Cc: Stefan Monnier

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




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Emacs locks up
  2021-06-20 16:05   ` Joe Riel
@ 2021-06-20 16:11     ` Emanuel Berg via Users list for the GNU Emacs text editor
  0 siblings, 0 replies; 5+ messages in thread
From: Emanuel Berg via Users list for the GNU Emacs text editor @ 2021-06-20 16:11 UTC (permalink / raw)
  To: help-gnu-emacs

Joe Riel wrote:

> `kill -SIGUSR2` did restore emacs [...]

It should be enough/the same with just -USR2 or even -12
(12 is the signal number of USR2).

You can get the number with 'kill -l USR2' or verify with
'kill -l 12'.

-- 
underground experts united
https://dataswamp.org/~incal




^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-06-20 16:11 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2021-06-20 16:11     ` Emanuel Berg via Users list for the GNU Emacs text editor

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).