Re: annoying behavior of emacs --daemon

["Liang Wang" <netcasper@gmail.com>]

On Tue, Nov 4, 2008 at 5:47 PM, Miles Bader <miles@gnu.org> wrote:
>
> On Tue, Nov 4, 2008 at 5:55 PM, Dan Nicolaescu <dann@ics.uci.edu> 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.
>
>

I got same problem.  And I found a patch at
http://www.nabble.com/segfault-when-using-XIM-with-multi-tty-on-gnu-linux-td18966793.html.
 It works for me.