From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9366 invoked by alias); 23 Apr 2014 17:56:46 -0000 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 Received: (qmail 9356 invoked by uid 89); 23 Apr 2014 17:56:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: nbfkord-smmo06.seg.att.com Received: from nbfkord-smmo06.seg.att.com (HELO nbfkord-smmo06.seg.att.com) (209.65.160.94) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 23 Apr 2014 17:56:44 +0000 Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.1-0) over TLS secured channel with ESMTP id adef7535.0.2675654.00-2056.7503755.nbfkord-smmo06.seg.att.com (envelope-from ); Wed, 23 Apr 2014 17:56:44 +0000 (UTC) X-MXL-Hash: 5357fedc60af15d9-3ee84341ad7398371ed513ea7693eb08e944625c Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id s3NHufCA017346 for ; Wed, 23 Apr 2014 10:56:41 -0700 Received: from flpi488.ffdc.sbc.com (flpi488.ffdc.sbc.com [130.4.162.182]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id s3NHuZaW017323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 23 Apr 2014 10:56:36 -0700 Received: from CAFRFD1MSGHUB9C.ITServices.sbc.com (CAFRFD1MSGHUB9C.itservices.sbc.com [135.161.21.163]) by flpi488.ffdc.sbc.com (RSA Interceptor) for ; Wed, 23 Apr 2014 17:56:17 GMT Received: from CAFRFD1MSGUSRIA.ITServices.sbc.com ([169.254.1.196]) by CAFRFD1MSGHUB9C.ITServices.sbc.com ([135.161.21.163]) with mapi id 14.03.0174.001; Wed, 23 Apr 2014 10:56:17 -0700 From: "KARR, DAVID" To: "cygwin@cygwin.com" Subject: RE: Fatal error from Cygwin emacs-w32 every day or so Date: Wed, 23 Apr 2014 17:56:00 -0000 Message-ID: References: <534B2EFE.4010509@cornell.edu> <534CB0AF.2040504@cornell.edu> <83y4z7jcb3.fsf@gnu.org> <534D5AB8.6030201@cornell.edu> <535308D8.1070200@cornell.edu> <5354FDD8.9090605@cornell.edu> <535564A4.2020302@cornell.edu> <5357E03B.8060205@cornell.edu> In-Reply-To: <5357E03B.8060205@cornell.edu> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-RSA-Inspected: yes X-RSA-Classifications: public X-AnalysisOut: [v=2.0 cv=QZ3RSLnv c=1 sm=1 a=xwOvzTHDVLE4u4nGvK72ag==:17 a] X-AnalysisOut: [=94PlVXF_xlIA:10 a=ofMgfj31e3cA:10 a=sQVNTnci9XEA:10 a=BLc] X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R] X-AnalysisOut: [AAAA:8 a=v_eIKD0wAAAA:8 a=w_pzkKWiAAAA:8 a=IcM1YT-TRlq8Cq5] X-AnalysisOut: [ssAMA:9 a=CjuIK1q_8ugA:10 a=2TSDkfqdCjIA:10 a=66msUWWtX2wA] X-AnalysisOut: [:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-IsSubscribed: yes X-SW-Source: 2014-04/txt/msg00525.txt.bz2 > -----Original Message----- > Of Ken Brown > Sent: Wednesday, April 23, 2014 8:46 AM > Subject: Re: Fatal error from Cygwin emacs-w32 every day or so >=20 > On 4/23/2014 10:03 AM, KARR, DAVID wrote: > >> -----Original Message----- > >> Of KARR, DAVID > >> Sent: Monday, April 21, 2014 7:21 PM > >> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so > >> > >> *** Security Advisory: This Message Originated Outside of AT&T ***. > >> Reference http://cso.att.com/EmailSecurity/IDSP.html for more > information. > >> > >>> -----Original Message----- > >>> Of Ken Brown > >>> Sent: Monday, April 21, 2014 11:34 AM > >>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so > >>> > >>> On 4/21/2014 1:25 PM, KARR, DAVID wrote: > >>>>> -----Original Message----- > >>>>> Of Ken Brown > >>>>> Sent: Monday, April 21, 2014 4:16 AM > >>>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so > >>>>> > >>>>> On 4/21/2014 1:14 AM, KARR, DAVID wrote: > >>>>>>> -----Original Message----- > >>>>>>> Of KARR, DAVID > >>>>>>> Sent: Saturday, April 19, 2014 6:19 PM > >>>>>>> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so > >>>>>>> > >>>>>>>> -----Original Message----- > >>>>>>>> Of Ken Brown > >>>>>>>> Sent: Saturday, April 19, 2014 4:38 PM > >>>>>>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so > >>>>>>>> > >>>>>>>> On 4/15/2014 12:13 PM, Ken Brown wrote: > >>>>>>>>> On 4/15/2014 12:12 AM, Eli Zaretskii wrote: > >>>>>>>>>>> Date: Mon, 14 Apr 2014 21:08:15 -0700 > >>>>>>>>>>> From: Ken Brown > >>>>>>>>>>> > >>>>>>>>>>>> I just saw it die, and this is the bt I get: > >>>>>>>>>>>> > >>>>>>>>>>>> Program received signal SIGSEGV, Segmentation fault. > >>>>>>>>>>>> 0x0000000100551354 in wait_reading_process_output ( > >>>>>>>>>>>> time_limit=3Dtime_limit@entry=3D0, nsecs=3Dnsecs@en= try=3D0, > >>>>>>>>>>>> read_kbd=3Dread_kbd@entry=3D-1, > >>>>> do_display=3Ddo_display@entry=3Dtrue, > >>>>>>>>>>>> wait_for_cell=3Dwait_for_cell@entry=3D4304630834, > >>>>>>>>>>>> wait_proc=3Dwait_proc@entry=3D0x0, > >>>>>>>>>>>> just_wait_proc=3Djust_wait_proc@entry=3D0) > >>>>>>>>>>>> @/usr/src/debug/emacs-24.3-7/src/process.c:4677 > >>>>>>>>>>>> 4677 if (wait_proc->gnutls_p /* Check > for > >>>>>>> valid > >>>>>>>>>>>> process. */ > >>>>>>>>>>> > >>>>>>>>>>> This backtrace doesn't make sense. If you look at the source > >>> code, > >>>>>>>>>>> you'll see that if wait_proc is NULL on entry to > >>>>>>>>>>> wait_reading_process_output, then line 4677 is never reached. > >>> I'm > >>>>>>> not > >>>>>>>>>>> sure what would cause a bogus backtrace like this. BLODA? > >>>>>>>>>>> Optimization? > >>>>>>>>>>> > >>>>>>>>>>> In any case, I suggest that you wait a week until I have a > >> chance > >>>>> to > >>>>>>>>>>> build a pretest of 24.4 for you to try. I'll build it without > >>>>>>>>>>> optimization to make debugging easier. > >>>>>>>>>> > >>>>>>>>>> This is a known problem with GnuTLS support, it was solved in > >> the > >>>>>>>>>> Emacs repository last November (bzr revision 114956, if someone > >>>>> wants > >>>>>>>>>> the diffs), and surely should be solved in the upcoming Emacs > >>> 24.4. > >>>>>>>>> > >>>>>>>>> Thanks, Eli! In that case I'll make a new release of emacs-24.3 > >>> with > >>>>>>>>> that patch applied, to see if it resolves the issue for the OP. > >>>>>>>> > >>>>>>>> I've rebuilt emacs-24.3 with the gnutls fix. David and Achim > (and > >>>>>>>> anyone else who's been experiencing these crashes), please try > the > >>>>>>>> following binary and let me know if it solves the problem: > >>>>>>>> > >>>>>>>> http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz > >>>>>>>> > >>>>>>>> You might have to do "chmod +x emacs-w32.exe" after uncompressing > >>> it. > >>>>>>>> > >>>>>>>> If it fixes the problem, I'll issue a new release of emacs-24.3. > >> If > >>>>>>>> not, I'll build a pretest of emacs-24.4 for you to try. > >>>>>>> > >>>>>>> Ok. It's running. As it only fails after random intervals, I'll > >>> have > >>>>> to > >>>>>>> keep it running for a while. I'll give it a day or so. > >>>>>> > >>>>>> I came back to my computer and saw two dialogs, one saying that my > >> VPN > >>>>> connection had died (that happens from time to time), and the other > >> the > >>>>> Emacs failure dialog. I started this executable from gdb, but it's > >>> saying > >>>>> that it doesn't have symbols, so the stacktrace probably isn't > >> helpful, > >>>>> but this is what I saw: > >>>>> > >>>>> Right. I just supplied a stripped binary for a quick test. It's > not > >>>>> suitable for debugging. > >>>>> > >>>>>> I've started it again, but not in gdb this time. > >>>>> > >>>>> If it crashes again, I'll build a pretest of 24.4 without > >> optimization > >>>>> and issue it as a test release. > >>>> > >>>> It just failed again while sitting here in my office (no relation to > >>> VPN/network issues). > >>> > >>> Could you try one more thing if you haven't already: Start emacs with > >>> the -Q option, in case there's something in your initialization files > >>> that triggers the problem. > >> > >> I started both a regular instance and the "-Q" instance around noon > today > >> (7 hours ago). The regular instance failed once since then, which I > >> restarted. The Q instance hasn't failed yet. That's not a definite, > but > >> it's lasted longer so far. Note that I haven't changed my .emacs in a > >> very long time. > > > > The regular instance has failed several times in the last couple of > days, whereas the "-Q" one still hasn't failed once. >=20 > OK, we've made progress. The next step is to bisect your .emacs and > find what it is that's triggering the failure. You might have to also > check your site-lisp directories (/usr/share/emacs/site-lisp and > /usr/share/emacs/24.3/site-lisp) if you've done any customization in them. (I really do dislike the spam filter on this list. Failing because of "cyg= win" at "cygwin.com" in the body is really annoying.) Ok. This is going to be a long process. I know I haven't hacked in /usr/s= hare, so that's safe.=20=20 -- 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