[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: annoying behavior of emacs --daemon
From: |
Miles Bader |
Subject: |
Re: annoying behavior of emacs --daemon |
Date: |
Tue, 4 Nov 2008 18:47:08 +0900 |
On Tue, Nov 4, 2008 at 5:55 PM, Dan Nicolaescu <address@hidden> wrote:
> > > > When using --daemon, you initially have no frames. You can then make
> > > > new frames with emacsclient -c or emacsclient -t, but if they're X
> > > > frames, closing the last such created frame (with C-x # or C-x C-c)
> > > > kills the emacs process!
>
> I still cannot reproduce this, with emacs freshly checked out and after
> a "make maintainer-clean" and /bin/rm -f /tmp/emacs*/server
>
> Can you please try to debug and find out why emacs dies for you?
Hmm, it seems to segfault in xlib, though I'm not sure why. I'm using
a gtk emacs; are you also?
1509 if (terminal->reference_count == 0)
(gdb) n
1515 Fdelete_terminal (tmp, NILP (force) ? Qt : force);
(gdb) n
Program received signal SIGSEGV, Segmentation fault.
0xb780dfc0 in _XSend () from /usr/lib/libX11.so.6
(gdb) ba
#0 0xb780dfc0 in _XSend () from /usr/lib/libX11.so.6
#1 0xb780e1b2 in _XFlush () from /usr/lib/libX11.so.6
#2 0xb77e5d71 in XFlush () from /usr/lib/libX11.so.6
#3 0xb7839700 in ?? () from /usr/lib/libX11.so.6
#4 0x0881a940 in ?? ()
#5 0xb78b53ec in ?? () from /usr/lib/libX11.so.6
#6 0xbfffb188 in ?? ()
#7 0xb7838de2 in _XimFlush () from /usr/lib/libX11.so.6
Backtrace stopped: frame did not save the PC
Lisp Backtrace:
"delete-frame" (0xbfffc374)
"server-delete-client" (0xbfffc4b4)
"server-save-buffers-kill-terminal" (0xbfffc5e4)
"save-buffers-kill-terminal" (0xbfffc764)
"call-interactively" (0xbfffc924)
-Miles
--
Do not taunt Happy Fun Ball.