From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "=?ISO-8859-1?Q?Zsitvai_J=E1nos?=" Newsgroups: gmane.emacs.devel Subject: Re: segfault when using XIM with multi-tty on gnu/linux Date: Sat, 13 Dec 2008 18:18:50 +0100 Message-ID: <29ba8f210812130918q6fcab179id7b978a90c4d4f50@mail.gmail.com> References: <87abb0bow8.fsf@cyd.mit.edu> <29ba8f210812130303x4110cf29j2be1387e606afee3@mail.gmail.com> <87vdto5e0w.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1229188754 19669 80.91.229.12 (13 Dec 2008 17:19:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Dec 2008 17:19:14 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Chong Yidong" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 13 18:20:17 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 1LBY9z-0006YA-EA for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2008 18:20:11 +0100 Original-Received: from localhost ([127.0.0.1]:41990 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBY8n-0002al-IJ for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2008 12:18:57 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LBY8i-0002a9-VV for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:18:53 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LBY8i-0002Zt-87 for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:18:52 -0500 Original-Received: from [199.232.76.173] (port=48967 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBY8i-0002Zq-2t for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:18:52 -0500 Original-Received: from mail-bw0-f12.google.com ([209.85.218.12]:35216) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LBY8h-0000IQ-Mw for emacs-devel@gnu.org; Sat, 13 Dec 2008 12:18:51 -0500 Original-Received: by bwz5 with SMTP id 5so4103920bwz.18 for ; Sat, 13 Dec 2008 09:18:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=WzR3eZgswZIQ4d9TqsQ+rgYLIOXDRGZBmfZbGIMIY1g=; b=Qrzn6ciucjIdvEnjOaTFy1aXOhhEXxDC2tDY4Bf5wkh6KI39AZvuZahhlUWmgIuHSi JoS260cHvYF84puEzV/It/dbX4G6YFIxAWYIQYwwonbqf21GcdpAw8tfY54DLOMvqRZy 0NfpLJxbnl+kncbj64eDw32vVLixVS4QDIf4Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=gJKOeezz7y4tkDLWTQ1n6R1Lx3tY9QzkPgkJfj+UuGfOBbpSXKTc1kxjvDQe6L7NrL rkDJpGXgbICerF2G5op7SmVqWIDlNQJE2tvB0B9iY7VjR2Uwq7Ex1L/NuHq+uCdDdbb3 mqU8LLMcg+u3QmC3bv5fzzuo2s3ckIfOPCbOc= Original-Received: by 10.181.52.14 with SMTP id e14mr1772389bkk.47.1229188730193; Sat, 13 Dec 2008 09:18:50 -0800 (PST) Original-Received: by 10.181.233.1 with HTTP; Sat, 13 Dec 2008 09:18:50 -0800 (PST) In-Reply-To: <87vdto5e0w.fsf@cyd.mit.edu> Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:106879 Archived-At: On Sat, Dec 13, 2008 at 15:46, Chong Yidong wrote: > Does the following patch change anything? > > If not, could you run Emacs under a debugger with breakpoints at > xim_close_dpy and xim_destroy_callback? Is xim_destroy_callback called > during frame deletion? If not, could you verify that XIMClose is called > by Emacs exactly once per frame deletion? Sadly, the patch did not fix it. I set breakpoints at xterm.c:8203 and xterm.c:10529 where xim_close_dpy and xim_destroy_callback are called. 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.