From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "djh" Newsgroups: gmane.emacs.devel Subject: Re: cygwn 5.19 with X-win bootstrap Date: Tue, 20 Jun 2006 17:49:09 +0900 Message-ID: <20060620174909.3676@henman-np.b-eng.it.to-be.co.jp> References: <20060525133349.1416@henman-np.b-eng.it.to-be.co.jp> <20060526134758.2944@henman-np.b-eng.it.to-be.co.jp> <20060530160319.2416@henman-np.b-eng.it.to-be.co.jp> <20060601135647.3404@henman-np.b-eng.it.to-be.co.jp> <20060602180327.2956@henman-np.b-eng.it.to-be.co.jp> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1150793514 26001 80.91.229.2 (20 Jun 2006 08:51:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 20 Jun 2006 08:51:54 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 20 10:51:49 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FsbxG-0005kp-AH for ged-emacs-devel@m.gmane.org; Tue, 20 Jun 2006 10:51:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FsbxG-00052G-1n for ged-emacs-devel@m.gmane.org; Tue, 20 Jun 2006 04:51:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FsbvD-00043X-7H for emacs-devel@gnu.org; Tue, 20 Jun 2006 04:49:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FsbvA-00041R-EZ for emacs-devel@gnu.org; Tue, 20 Jun 2006 04:49:18 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FsbvA-00041L-8Z for emacs-devel@gnu.org; Tue, 20 Jun 2006 04:49:16 -0400 Original-Received: from [219.127.155.130] (helo=ns-2.to-be.co.jp) by monty-python.gnu.org with smtp (Exim 4.52) id 1Fsc5d-0003TR-MG for emacs-devel@gnu.org; Tue, 20 Jun 2006 05:00:06 -0400 Original-Received: (qmail 90953 invoked from network); 20 Jun 2006 17:49:10 +0900 Original-Received: from unknown (HELO imss-3.it.to-be.co.jp) (10.128.1.23) by ns-2.to-be.co.jp with SMTP; 20 Jun 2006 17:49:10 +0900 Original-Received: (qmail 20272 invoked from network); 20 Jun 2006 17:49:10 +0900 Original-Received: from localhost (HELO imss-3.it.to-be.co.jp) (127.0.0.1) by localhost with SMTP; 20 Jun 2006 17:49:10 +0900 Original-Received: (qmail 20269 invoked by alias); 20 Jun 2006 17:49:09 +0900 Original-Received: (qmail 20261 invoked from network); 20 Jun 2006 17:49:09 +0900 Original-Received: from unknown (HELO henman-np.b-eng.it.to-be.co.jp) (10.137.6.76) by imss-3.it.to-be.co.jp with SMTP; 20 Jun 2006 17:49:09 +0900 Original-To: Original-cc: In-reply-to: Your message of Fri, 02 Jun 2006 12:27:28 +0300 X-Mailer: MH-E 8.0; GNU Mailutils 0.6.94; GNU Emacs 22.0.50 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:56024 Archived-At: Eli, et al, sorry I was sent out of town for some testing and was unable to continue with testing cvs emasc with cygwin using x-widows. I have taken up the matter with cygwin people and will upgrade to try using newer (not yet released versions) of cygwin and gdb , which is reported be better. The older versions reported SIGSEGV when it wasn't really the case.... I report again when I find out more info. Thanks for your support. Darel Henman Re: > . .... > So it crashes inside pthread_mutexattr_init, which is called from > within uninterrupt_malloc. Just to be sure, perhaps step into > uninterrupt_malloc and see whether my conclusion is correct, and which > of the two calls to pthread_mutexattr_init crashes. > > If my conclusion is right, I think you need to take this up with > Cygwin maintainers. Perhaps, if you show them the code in > uninterrupt_malloc that calls pthread functions, they will be able to > figure out the problem. > > Thanks for looking into this. >