Re: segfault when using XIM with multi-tty on gnu/linux

[Chong Yidong]

"Zsitvai János" <address@hidden> writes:

> xim_close_dpy never got called, and xim_destroy_callback was called
> only when creating an X frame.
>
> The XCloseIM breakpoint at xterm.c:8328 claims that it was hit 3
> times: once after deleting the first X frame, twice after deleting the
> second.

What are the backtraces where XCloseIM was called (with my patch
applied)?

With the patch, XCloseIM is called only if dpyinfo->xim in non-NULL, and
dpyinfo->xim is set to NULL after calling XCloseIM.  So I would like to
know why XCloseIM is called again.