Re: annoying behavior of emacs --daemon

[Miles Bader <miles@gnu.org>]

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

"Liang Wang" <netcasper@gmail.com> writes:
>> Hmm, it seems to segfault in xlib, though I'm not sure why.  I'm using
>> a gtk emacs; are you also?
>
> 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.

Ah, that patch fixes the problem for me too!  Thank you!

[I've attached a version of the patch which applies correctly
(nabble mucks up the whitespace).]

-Miles


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch to fix xlib crash --]
[-- Type: text/x-diff, Size: 487 bytes --]

--- orig/src/xterm.c
+++ mod/src/xterm.c
@@ -8319,9 +8319,11 @@
 	XUnregisterIMInstantiateCallback (dpyinfo->display, dpyinfo->xrdb,
 					  NULL, EMACS_CLASS,
 					  xim_instantiate_callback, NULL);
-#endif /* not HAVE_X11R6_XIM */
+#else /* not HAVE_X11R6_XIM */
+      /* if we have X11R6 xim, this causes a double-free */
       if (dpyinfo->display)
 	XCloseIM (dpyinfo->xim);
+#endif /* not HAVE_X11R6_XIM */
       dpyinfo->xim = NULL;
       XFree (dpyinfo->xim_styles);
     }

[-- Attachment #3: Type: text/plain, Size: 127 bytes --]



-- 
`Suppose Korea goes to the World Cup final against Japan and wins,' Moon said.
`All the past could be forgiven.'   [NYT]