From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Gary Mills Newsgroups: gmane.emacs.bugs Subject: Re: emacs-22.1 with GTK dumps core when Gnome wigets clicked Date: Sat, 16 Jun 2007 08:32:52 -0500 Message-ID: <20070616133252.GA9378@cc.umanitoba.ca> References: <200706091549.l59FnfHJ005433@deneb.cc.umanitoba.ca> <20070610125120.GA27355@cc.umanitoba.ca> <20070610.224832.46203780.mituharu@math.s.chiba-u.ac.jp> <20070610141003.GA12085@cc.umanitoba.ca> <20070614184924.GA25414@cc.umanitoba.ca> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1182000794 20894 80.91.229.12 (16 Jun 2007 13:33:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 16 Jun 2007 13:33:14 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org To: YAMAMOTO Mitsuharu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jun 16 15:33:13 2007 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HzYOu-0001Hv-UU for geb-bug-gnu-emacs@m.gmane.org; Sat, 16 Jun 2007 15:33:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HzYOu-0001ok-FU for geb-bug-gnu-emacs@m.gmane.org; Sat, 16 Jun 2007 09:33:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HzYOg-0001aB-Q1 for bug-gnu-emacs@gnu.org; Sat, 16 Jun 2007 09:32:58 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HzYOe-0001XL-9s for bug-gnu-emacs@gnu.org; Sat, 16 Jun 2007 09:32:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HzYOe-0001Wv-2f for bug-gnu-emacs@gnu.org; Sat, 16 Jun 2007 09:32:56 -0400 Original-Received: from electra.cc.umanitoba.ca ([130.179.16.23]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HzYOd-0000bq-Mr for bug-gnu-emacs@gnu.org; Sat, 16 Jun 2007 09:32:55 -0400 Original-Received: from deneb.cc.umanitoba.ca (mills@deneb.cc.umanitoba.ca [130.179.16.69]) by electra.cc.umanitoba.ca (8.13.0/8.13.0) with ESMTP id l5GDWs5q009263; Sat, 16 Jun 2007 08:32:54 -0500 (CDT) Original-Received: (from mills@localhost) by deneb.cc.umanitoba.ca (8.13.8+Sun/8.12.2) id l5GDWqgn011627; Sat, 16 Jun 2007 08:32:52 -0500 (CDT) Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.10i X-detected-kernel: Solaris 9 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:15913 Archived-At: On Sat, Jun 16, 2007 at 02:22:54PM +0900, YAMAMOTO Mitsuharu wrote: > >>>>> On Thu, 14 Jun 2007 13:49:25 -0500, Gary Mills said: > > >> I found a possible problem, which may or may not be relevant to > >> this issue, in the initialization of the recursive mutex in > >> src/gmalloc.c. Could you try this patch? > > > I'm sorry to report that it still dumps core when I click on one of > > those icons. > > I've set up Solaris 10 11/06 SPARC with Sun Studio 11 and tried > making/running the GTK+ build, but couldn't reproduce the crash even > with unmodified Emacs 22.1. That may be because mine is a > uniprocessor machine. What about yours? That'll be it. I've run emacs-22.1 on both SPARC and x86 hardware, but never on a uniprocessor machine. We don't have any of those left. However, I just took one CPU offline on my Ultra 60 and tried emacs-22.1. When I click on the `Read and existing file' icon, the `Find File' dialogue window appears just like it should. When I click on that icon with both CPUs online, I get a very long pause, after which the emacs window disappears, leaving a 94-meg core file. > Could you try yet another patch below and identify the line in the > source code where the crash occurs? I'll see what I can do. -- -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-