X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Om6QGPBhEdFh5uAmLo9ewqQjPedlwqROZiaR7FQ8CJO
	KrCKbZMhjKFjLc8tzrjRXqdpdJtCpHHkFqbFEik6kEc+KDAzJQGQC4fcwWuzEv71
	IFjwX+Bz+s1kAbxf528pLhdHFDr8DMLofgOBj41xLD/0eLp21J6sV+9mikA71ThQ
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=Ie9ZwlG+nesYVsrUAoNTWqspMZo=; b=Z2luiZKXyl5iZ54tj
	9wqpg44sxEp7qLYCxpX/eWmAPvvUWwi1rs/usDkvt/V5NLhOqmFeQj9w+cClOWer
	oGJQ1+HJCQnYIeUVDBKePdLwY/Er4AqIs/834MsYl+vZEuVASdL5cAVEU8xtL1q5
	M6YI2qVIXtLltwgU/r3YnS8h8A=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RDNS_NONE,SPF_NEUTRAL autolearn=no version=3.3.1
Message-ID: <51FFC4F2.8080909@cs.utoronto.ca>
Date: Mon, 05 Aug 2013 11:29:54 -0400
From: Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 64-bit emacs crashes a lot
References: <51F3151D DOT 7040000 AT cs DOT utoronto DOT ca> <51F33565 DOT 1090406 AT cornell DOT edu> <51F33F52 DOT 4060405 AT cs DOT utoronto DOT ca> <51FB1D9E DOT 5090102 AT cs DOT utoronto DOT ca> <20130802080211 DOT GA18054 AT calimero DOT vinschen DOT de> <51FB9228 DOT 2020309 AT cornell DOT edu> <51FBA100 DOT 90005 AT cs DOT utoronto DOT ca> <51FD5462 DOT 5020400 AT cs DOT utoronto DOT ca> <51FFBDFF DOT 7040501 AT cornell DOT edu>
In-Reply-To: <51FFBDFF.7040501@cornell.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 05/08/2013 11:00 AM, Ken Brown wrote:
> On 8/3/2013 3:05 PM, Ryan Johnson wrote:
>> On 02/08/2013 8:07 AM, Ryan Johnson wrote:
>>> On 02/08/2013 7:04 AM, Ken Brown wrote:
>>>> On 8/2/2013 4:02 AM, Corinna Vinschen wrote:
>>>>> On Aug  1 22:46, Ryan Johnson wrote:
>>>>>> Here's a new one... I started a compilation, but before it actually
>>>>>> invoked the command it started pegging the CPU. After ^G^G^G, it
>>>>>> crashed with the following:
>>>>>>> Auto-save? (y or n) y
>>>>>>>       0 [main] emacs 5076 C:\cygwin64\bin\emacs-nox.exe: *** fatal
>>>>>>> error - Internal error: TP_NUM_W_BUFS too small 2268032 >= 10.
>>>>>
>>>>> That looks like a memory overwrite.  2268032 is 0x229b80, which looks
>>>>> suspiciously like a stack address.  And the overwritten value is 
>>>>> on the
>>>>> stack, too, well within the cygwin TLS area.  If *this* value gets
>>>>> overwritten, the TLS is probbaly totally hosed at this point. There's
>>>>> just no way to infer the culprit from this limited info.
>>>>
>>>> Could this be BLODA?  Ryan, I noticed that you wrote in a different
>>>> thread, "I recently migrated to 64-bit cygwin...and so far have not
>>>> had to disable Windows Defender; the latter was a recurring source of
>>>> trouble for my previous 32-bit cygwin install on Win7/64."
>>> This would be a whole new level of nasty from a BLODA... I thought
>>> they only interfered with fork()?
>>>
>>> However, this *is* Windows Defender we're talking about... service
>>> disabled and all cygwin processes restarted. I'll let you know in a
>>> day or so if the crashes go away.
>> Rats. I just had another crash, the "Fatal error 6" variety. Windows
>> Defender has not turned itself back on (it's been known to do that), and
>> a scan of the BLODA list didn't match anything else on my system.
>>
>> So I don't think it's BLODA...
>>
>> Ideas?
>
> Not really, other than the obvious: (a) Find a reproducible way of 
> making emacs-nox crash.  (b) Catch the crash in gdb by setting a 
> suitable break point.
I've had no luck with (a), but the latest version of gdb forwards 
signals properly (thanks cgf!), so I've got it watching in the 
background for anything to go wrong. If it's really a memory overwrite, 
though, the stack trace is unlikely to give much insight into root causes.

Ryan


--
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