From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12210 invoked by alias); 25 Jun 2012 16:28:56 -0000 Received: (qmail 12175 invoked by uid 22791); 25 Jun 2012 16:28:52 -0000 X-SWARE-Spam-Status: No, hits=-5.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_CG X-Spam-Check-By: sourceware.org Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 25 Jun 2012 16:28:39 +0000 Received: by bkty5 with SMTP id y5so3560896bkt.2 for ; Mon, 25 Jun 2012 09:28:38 -0700 (PDT) Received: by 10.204.152.137 with SMTP id g9mr4338485bkw.95.1340641718356; Mon, 25 Jun 2012 09:28:38 -0700 (PDT) Received: from [192.168.2.198] (93-33-97-203.ip44.fastwebnet.it. [93.33.97.203]) by mx.google.com with ESMTPS id m2sm47276548bkm.2.2012.06.25.09.28.05 (version=SSLv3 cipher=OTHER); Mon, 25 Jun 2012 09:28:18 -0700 (PDT) Message-ID: <4FE89194.6070204@gmail.com> Date: Mon, 25 Jun 2012 16:28:00 -0000 From: marco atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: crash on latest cygwin snapshot References: <4FE786DA.2050208@gmail.com> <20120625043110.GA28607@ednor.casa.cgf.cx> <4FE81478.8030508@gmail.com> <20120625080550.GC2976@calimero.vinschen.de> <4FE82361.8040908@gmail.com> <20120625090029.GE2321@calimero.vinschen.de> <4FE83122.8020406@gmail.com> <4FE85226.5020804@gmail.com> <20120625144551.GA4244@ednor.casa.cgf.cx> <4FE87D29.7080906@gmail.com> <20120625152916.GA9053@ednor.casa.cgf.cx> In-Reply-To: <20120625152916.GA9053@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-06/txt/msg00455.txt.bz2 On 6/25/2012 5:29 PM, Christopher Faylor wrote: > On Mon, Jun 25, 2012 at 05:00:57PM +0200, marco atzeri wrote: >> On 6/25/2012 4:45 PM, Christopher Faylor wrote: >>> On Mon, Jun 25, 2012 at 01:57:26PM +0200, marco atzeri wrote: >>>> On 6/25/2012 11:36 AM, marco atzeri wrote: >>>>> On 6/25/2012 11:00 AM, Corinna Vinschen wrote: >>>>>> On Jun 25 10:37, marco atzeri wrote: >>>>>>> >>>>>>> A normal exception should kill just the running process, while >>>>>>> I see that xprobe_comp, bash, mintty are killed and >>>>>>> also others bash and mintty processes are taking down. >>>>>> >>>>>> Really all processes or just all processes in the same terminal window? >>>>> >>>>> all processes in all the available terminal windows. >>>>> 3 mintty and 3 bash are taken down and they were indepedently >>>>> created by the start menu >>>>> >>>>>> >>>>>> Corinna >>>>>> >>>>> >>>>> I will check if today cgf's changeset make any difference >>>>> >>>>> Regards >>>>> Marco >>>>> >>>>> >>>> hi Corinna, >>>> no difference. It takes down everything >>>> >>>> but you are right about mintty, it is crashing and the stackdump >>>> are located at c:\windows\SySWOW64, I only noticed with procmon. >>>> >>>> --------------------------------------------------------------------- >>>> Exception: STATUS_ACCESS_VIOLATION at eip=610CE726 >>>> eax=610CE710 ebx=0000010C ecx=777B0000 edx=0008E3C8 esi=0028A5B8 >>>> edi=8005A088 >>>> ebp=0028A468 esp=0028A450 program=E:\cygwin\bin\mintty.exe, pid 6652, >>>> thread main >>>> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B >>>> Stack trace: >>>> Frame Function Args >>>> 0028A468 610CE726 (8004EF58, 0028A5B8, E65DA9C7, 231FFA3E) >>>> 0028A488 610D05CE (0028A5B8, 0028A648, 0028A540, 0028A520) >>>> 0028A618 610D146A (00000002, 0028A648, 0028A540, 0028A520) >>>> 24479433 [main] mintty 6652 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 24495658 [main] mintty 6652 exception::handle: Error while dumping state >>>> (probably corrupted stack) >>>> ---------------------------------------------------------------------- >>>> >>>> $ addr2line.exe -e cygwin1.dll 610CE726 >>>> /pub/cygwin/cvs/src_new/winsup/cygwin/select.cc:687 >>>> >>>> $ addr2line.exe -e cygwin1.dll 610D05CE >>>> /pub/cygwin/cvs/src_new/winsup/cygwin/select.cc:243 >>>> >>>> $ addr2line.exe -e cygwin1.dll 610D146A >>>> /pub/cygwin/cvs/src_new/winsup/cygwin/select.cc:252 >>> >>> How long did this take to crash mintty? >>> >>> cgf >>> >> >> >> 7 sec on my slow PC. >> From procmon I saw that xprobe_comp and the shells it reises continue >> to run for a while and only after they close. >> >> on 20120611 the full successful run is 45 sec. > > I let my run on 20120611 go for more than that. The system eventually > became unresponsive and I had to power cycle it. Probably I could have > rebooted via Start if I'd been more patient, though. > > I have another vague idea about this problem and will be checking in > another change soon. > > cgf > I straced mintty and uploaded the first portion, 10Mb, on http://matzeri.altervista.org/works/atlas/ the remaining 320 Mb have no further trace of mintty Regards Marco -- 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