From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: segfault when using XIM with multi-tty on gnu/linux Date: Sat, 13 Dec 2008 12:31:44 -0500 Message-ID: <8763lohthb.fsf@cyd.mit.edu> References: <87abb0bow8.fsf@cyd.mit.edu> <29ba8f210812130303x4110cf29j2be1387e606afee3@mail.gmail.com> <87vdto5e0w.fsf@cyd.mit.edu> <29ba8f210812130918q6fcab179id7b978a90c4d4f50@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1229189513 21870 80.91.229.12 (13 Dec 2008 17:31:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Dec 2008 17:31:53 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?Zsitvai_J=C3=A1nos?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 13 18:32:58 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LBYML-0002GJ-V8 for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2008 18:32:58 +0100 Original-Received: from localhost ([127.0.0.1]:55555 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBYLA-0003dv-Dp for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2008 12:31:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LBYL6-0003cy-5F for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:31:40 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LBYL4-0003cQ-RN for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:31:39 -0500 Original-Received: from [199.232.76.173] (port=42247 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBYL4-0003cJ-Id for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:31:38 -0500 Original-Received: from cyd.mit.edu ([18.115.2.24]:37683) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LBYL4-0001ss-7a for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:31:38 -0500 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id 56C1057E196; Sat, 13 Dec 2008 12:31:44 -0500 (EST) In-Reply-To: <29ba8f210812130918q6fcab179id7b978a90c4d4f50@mail.gmail.com> ("Zsitvai =?utf-8?Q?J=C3=A1nos=22's?= message of "Sat, 13 Dec 2008 18:18:50 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:106880 Archived-At: "Zsitvai J=C3=A1nos" 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.