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 00:55:03 -0500 Message-ID: <87abb0bow8.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1229147715 21636 80.91.229.12 (13 Dec 2008 05:55:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Dec 2008 05:55:15 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Smith Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 13 06:56:20 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 1LBNUB-0002AT-TN for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2008 06:56:20 +0100 Original-Received: from localhost ([127.0.0.1]:34568 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBNSz-0000rr-QO for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2008 00:55:05 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LBNSu-0000rm-Kj for emacs-devel@gnu.org; Sat, 13 Dec 2008 00:55:00 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LBNSs-0000ra-RD for emacs-devel@gnu.org; Sat, 13 Dec 2008 00:55:00 -0500 Original-Received: from [199.232.76.173] (port=60716 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBNSs-0000rX-Kf for emacs-devel@gnu.org; Sat, 13 Dec 2008 00:54:58 -0500 Original-Received: from cyd.mit.edu ([18.115.2.24]:45345) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LBNSs-0007fY-CV for emacs-devel@gnu.org; Sat, 13 Dec 2008 00:54:58 -0500 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id 17CCB57E04B; Sat, 13 Dec 2008 00:55:03 -0500 (EST) 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:106866 Archived-At: > Is the call to XCloseIM() in xim_close_dpy (xterm.c:8316) necessary? > Since if we HAVE_X11R6_XIM, xim_destroy_callback is called, and it > claims there is no need to call XCloseIM (xterm.c:8143). A small patch > is attached that changes the logic of xim_close_dpy slightly to call > XCloseIM iff HAVE_XIM && !HAVE_X11R6_XIM. This fixes the segfault > here. I reverted your patch, as it was causing a memory leak. > Steps to reproduce: > 1. start emacs -nw > 2. have XIM active for your X session (run scim -d) > 3. start X11-capable emacs frame with emacsclient -c > 4. close the X11 emacs frame > 5. segfault with error I can't reproduce this bug, even now that Emacs calls XCloseIM. Do you still see the segfault?