GNU bug report logs - #7149
23.2; exiting last `emacsclient -c' frame, and then rerun client, segfaults `emacs --daemon'

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 7149 in the body.
You can then email your comments to 7149 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Chen Levy <chenlevy <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Emacs 23.2.1: exiting last `emacsclient -c' frame, and then rerun
	client, segfaults `emacs --daemon'
Date: Sat, 2 Oct 2010 15:12:56 +0200

[Message part 1 (text/plain, inline)]

Description:
=======

When starting emacs server with `emacs --daemon', and connecting to it with
`emacsclient -c', then closing the last `emacsclient -c' frame and trying to
open a new `emacsclient -c' frame, the `emacs --daemon'
process receive SYSSEGV.

Steps to reproduce:
============

0. Make sure no Emacs processes are running.

1. Run: emacs --daemon
  It prints:
  ("emacs")
  Starting Emacs daemon.

  and the process starts normally.

2. Run: emacsclient -c
  It prints: Waiting for Emacs...
  and a new frame opens as expected.

3. Close the frame, started on strep 2.
  Observe that the `/tmp/emacs${UID}/server' socket seem to be active.
  `fuser' on it prints the `emacs --daemon' PID.

4. (optional) Open `gdb', `attach' to the `emacs --daemon' process, and
`continue' it.

5. Run: emacsclient -c
  It prints: Waiting for Emacs...
  but no new frame is opened.

  gdb prints something like:
  Program received signal SIGSEGV, Segmentation fault.
  0x00007f989f211527 in kill () from /lib/libc.so.6

  And the output of `fuser /tmp/emacs${UID}/server' confirms that the socket
is stale.

6. Run: `emacsclient -c' prints:
  emacsclient: connect: Connection refused
  emacsclient: No socket or alternate editor.  Please use:

          --socket-name
          --server-file      (or environment variable EMACS_SERVER_FILE)
          --alternate-editor (or environment variable ALTERNATE_EDITOR)

Version information:
============

# (version)
GNU Emacs 23.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.12.9)
(compiled from source)

# uname -a
Linux xxxxxx 2.6.24-28-generic #1 SMP Thu Sep 16 14:18:43 UTC 2010 x86_64
GNU/Linux

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04.4 LTS"

See also:
======

http://superuser.com/questions/194395/why-does-tmp-emacsuid-server-get-stale-after-last-emacsclient-exits

| Cheers,
| Chen.

[Message part 2 (text/html, inline)]

Message #8 received at 7149 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> gnu.org>
To: Chen Levy <chenlevy <at> gmail.com>
Cc: 7149 <at> debbugs.gnu.org
Subject: Re: bug#7149: Emacs 23.2.1: exiting last `emacsclient -c' frame,
	and then rerun client, segfaults `emacs --daemon'
Date: Fri, 20 Apr 2012 18:14:49 +0800

Chen Levy <chenlevy <at> gmail.com> writes:

> When starting emacs server with `emacs --daemon', and connecting to it
> with `emacsclient -c', then closing the last `emacsclient -c' frame
> and trying to open a new `emacsclient -c' frame, the `emacs --daemon'
> process receive SYSSEGV.
>
> 1. Run: emacs --daemon
> 2. Run: emacsclient -c
> 3. Close the frame, started on strep 2.
> 5. Run: emacsclient -c
>   It prints: Waiting for Emacs...
>   but no new frame is opened.

I'm sorry that no one got back to you on this, but I can't reproduce it
on either Emacs 23.4 or the latest Emacs repository.  I think this must
have been fixed in the meantime; please let us know if you still
experience the behavior.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.