From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: connecting to a lost server process
Date: Fri, 12 Jul 2019 10:54:28 +0300 [thread overview]
Message-ID: <83r26v3cy3.fsf@gnu.org> (raw)
In-Reply-To: <20190712062057.15599.qmail@localhost.localdomain> (message from Madhu on 12 Jul 2019 06:20:57 -0000)
> Date: 12 Jul 2019 06:20:57 -0000
> From: Madhu <enometh@meer.net>
>
> The socket is still open as can be seen in /proc/<emacspid>/fd/ - is
> there some linux arcana that can be exploited to connect to it?
>
> Earlier it used to be possible to gdb attach to the emacs process and
> to restart the server. Something like
> Feval(Fcar(Fread_from_string(build_string("(server-start)"),Qnil,Qnil)),Qnil)
> But for some time now that route hits a
> terminate_due_to_signal. (Apparently make-network-process tries to
> signal an error which calls emacs_abort which ends the show)
Please report a bug with the details of that crash, it may or may not
be a bug.
> [Unfortunately recently the robustness of the server mechanism has gone
> down - (especially since elogind). Typically I set
> XDG_RUNTIME_DIR=/dev/shm/<username> in my environment and start a
> server which i expect to survive restarts in dbus, elogind etc. That
> seems no longer possible even when using a --without-x emacs.]
Did you try to bind a function to sigusr1 or sigusr2 event, and have
that function restore the server file?
next prev parent reply other threads:[~2019-07-12 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 6:20 connecting to a lost server process Madhu
2019-07-12 7:54 ` Eli Zaretskii [this message]
[not found] ` <mailman.985.1562918079.2688.help-gnu-emacs@gnu.org>
2019-07-14 12:00 ` bug#36648: emacs signals under gdb - [Re: " Madhu
2019-07-18 5:35 ` Eli Zaretskii
2019-07-18 14:58 ` Madhu
2019-07-18 15:24 ` Eli Zaretskii
2019-07-19 1:53 ` Madhu
2019-07-19 6:53 ` Eli Zaretskii
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=83r26v3cy3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.