From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: emacs --daemon and GDK default display Date: Tue, 17 Mar 2009 19:47:33 +0800 Message-ID: <49BF8DD5.2030502@gnu.org> References: <18879.34340.349741.391197@a1ihome1.kph.uni-mainz.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1237290511 16462 80.91.229.12 (17 Mar 2009 11:48:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 17 Mar 2009 11:48:31 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ulrich Mueller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 17 12:49:47 2009 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 1LjXnm-0008S1-0y for ged-emacs-devel@m.gmane.org; Tue, 17 Mar 2009 12:49:46 +0100 Original-Received: from localhost ([127.0.0.1]:53815 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LjXmP-00052h-QS for ged-emacs-devel@m.gmane.org; Tue, 17 Mar 2009 07:48:21 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LjXmD-0004x0-Ec for emacs-devel@gnu.org; Tue, 17 Mar 2009 07:48:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LjXm8-0004tg-F8 for emacs-devel@gnu.org; Tue, 17 Mar 2009 07:48:08 -0400 Original-Received: from [199.232.76.173] (port=52061 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LjXm8-0004tK-4D for emacs-devel@gnu.org; Tue, 17 Mar 2009 07:48:04 -0400 Original-Received: from wf-out-1314.google.com ([209.85.200.169]:57634) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LjXm6-0007y8-EI for emacs-devel@gnu.org; Tue, 17 Mar 2009 07:48:03 -0400 Original-Received: by wf-out-1314.google.com with SMTP id 28so3475984wfc.24 for ; Tue, 17 Mar 2009 04:48:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=2sz4IAnGXIlP9cdzzP6KTE9cvGjC7p85vSTYekJ+r/4=; b=xLWn5yjM5nkT/5zlokZbTY2jHmWQeNlD1hTNstL809PfVNGI0BMe+1PTUVuDycdnrI JozRhRnVBnnV3onhk8D/XBO/fNNwAKZ4qU4b+SsKduWhH4MHPtYFoG86BgLVDUEg3RHa gspVbWG0MWf+/uF12VKBXlYt31tEmXhNAILXE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=d2MwzYnxMaZAnhdCCoxNo6AAA6DrPVubcLaG7P5IbiXy0AZgZI3DQm/ppmoh2mIpq5 OUguDhZAUOXrdeVgP8l9BDljEZKeyc1DfzM7nTg6r/OBwsgHmgBOtSQPyDqtl73ObifP A15CvVatDvgbbpDca+WfRC/Bk9RsvcFCWkhRY= Original-Received: by 10.142.89.13 with SMTP id m13mr2698917wfb.50.1237290480386; Tue, 17 Mar 2009 04:48:00 -0700 (PDT) Original-Received: from ?192.168.249.26? ([118.101.24.182]) by mx.google.com with ESMTPS id 29sm14223737wfg.13.2009.03.17.04.47.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 17 Mar 2009 04:47:59 -0700 (PDT) User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) In-Reply-To: <18879.34340.349741.391197@a1ihome1.kph.uni-mainz.de> 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:109668 Archived-At: Ulrich Mueller wrote: > While I think that the blame is with libcanberra, I'm confused about > the fact that the segfault only happens during the second request from > a client. Does it mean that there is a GDK default display at the time > of the first request, but not for the second one? Why? > Just a guess without looking at libcanberra, but could the bug be that libcanberra remembers the default display created during the first request and tries to reuse it after it is closed?