X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18WHjamRJjcnGs9P3xiPvM5
Date: Thu, 2 Aug 2012 23:41:19 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: crash on latest cygwin snapshot
Message-ID: <20120803034119.GA15831@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <50190645.2050209@gmail.com> <20120801122902.GC17949@calimero.vinschen.de> <50192522.4090507@cornell.edu> <20120801125834.GH17949@calimero.vinschen.de> <501A946A.2030102@cornell.edu> <87zk6dcgfg.fsf@Rainer.invalid> <20120802182129.GA11728@ednor.casa.cgf.cx> <87r4rpcdhx.fsf@Rainer.invalid> <20120802193416.GB11728@ednor.casa.cgf.cx> <501B3FE6.90006@cornell.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <501B3FE6.90006@cornell.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Thu, Aug 02, 2012 at 11:05:10PM -0400, Ken Brown wrote:
>On 8/2/2012 3:34 PM, Christopher Faylor wrote:
>> On Thu, Aug 02, 2012 at 09:14:50PM +0200, Achim Gratz wrote:
>>> Christopher Faylor writes:
>>>> Just to be clear: Is this with the recent snapshot?
>>>
>>> Yes, this is with the 2012-08-01 snapshot.
>>>
>>>> I ask because one other "I see something similar" seemed to come from
>>>> 1.7.16.
>>>
>>> I'm almost always running a snapshot, but I can back it out to vanilla
>>> Cygwin or any other snapshot if it helps finding the error.  I don't
>>> think I've had any other updates except mesa inbetween switching from
>>> the snapshot I used before and the current one ??? but that is
>>> circumstancial evidence only.
>>
>> It would be interesting to see if you or Ken have a problem with the
>> 20120730 snapshot.
>>
>> And, if so, then an strace would probably be useful, although it would
>> be huge.  If you do get one, let me know how to download it or I can
>> provide temporary storage somewhere.
>
>I do have the same problem with the 20120730 snapshot.  I started emacs 
>in an xterm window, attached strace, and walked away.  This time it 
>didn't take long for emacs to crash, so the strace output isn't huge:
>
>wget http://sanibeltranquility.com/cygwin/strace.out

Thanks.  I think I see the problem but I won't be able to get to it tonight.

It's in the new signal handling code.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

