From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4897 invoked by alias); 1 Nov 2011 21:50:55 -0000 Received: (qmail 4885 invoked by uid 22791); 1 Nov 2011 21:50:52 -0000 X-SWARE-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_YG X-Spam-Check-By: sourceware.org Received: from nm5-vm0.bullet.mail.sp2.yahoo.com (HELO nm5-vm0.bullet.mail.sp2.yahoo.com) (98.139.91.204) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Tue, 01 Nov 2011 21:50:37 +0000 Received: from [98.139.91.67] by nm5.bullet.mail.sp2.yahoo.com with NNFMP; 01 Nov 2011 21:50:36 -0000 Received: from [98.139.91.49] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 01 Nov 2011 21:50:36 -0000 Received: from [127.0.0.1] by omp1049.mail.sp2.yahoo.com with NNFMP; 01 Nov 2011 21:50:36 -0000 Received: (qmail 67792 invoked by uid 60001); 1 Nov 2011 21:50:35 -0000 Received: from [209.204.163.4] by web114404.mail.gq1.yahoo.com via HTTP; Tue, 01 Nov 2011 14:50:35 PDT References: <1319954770.81475.YahooMailNeo@web114412.mail.gq1.yahoo.com> <4EAEB486.5090002@dronecode.org.uk> <1320088071.46008.YahooMailNeo@web114420.mail.gq1.yahoo.com> <1320088928.33967.YahooMailNeo@web114410.mail.gq1.yahoo.com> <4EAFF999.7010301@dronecode.org.uk> Message-ID: <1320184235.73485.YahooMailNeo@web114404.mail.gq1.yahoo.com> Date: Tue, 01 Nov 2011 21:50:00 -0000 From: Dave Reply-To: Dave Subject: Re: -nolisten tcp -multiwindow combination crashes in XWin startup To: cygwin-xfree , "cygwin@cygwin.com" In-Reply-To: <4EAFF999.7010301@dronecode.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2011-11/txt/msg00004.txt.bz2 Jon:=A0 Thanks for the=A0pointers to the fork() problem faqs.=A0 That and a= bit of googling led=A0me to give rebaseall a try, and that appears to have cured my issue.=A0 (For others, instructions can be fo= und at http://www.heikkitoivonen.net/blog/2008/11/26/cygwin-upgrades-and-rebaseall= /=A0.) Suggestion, perhaps more to the main cygwin team:=A0 Since this issue is cy= gwin specific and=A0is a bit obscure (I've been using cygwin for a good many years, but this is the first time I've re= cognized I had issues from this), it'd be nice if users didn't have to learn about this the hard way.=A0 Could running=A0r= ebaseall perhaps be automated as part of setup.com? ----- Original Message ----- From: Jon TURNEY Sent: Tuesday, November 1, 2011 6:52 AM Subject: Re: -nolisten tcp -multiwindow combination crashes in XWin startup On 31/10/2011 19:22, Dave wrote: > Sadly this one wants to play a little hard to get... >=20 > I have tried this on two somewhat similar machines - 5 years difference i= n hardware, but both XP Pro up-to-date on Microsoft Update, and both runnin= g the cygwin versions present on mirror.mcs.anl.gov as of this weekend - bo= th were upgraded, then after both were, I checked that there were no furthe= r upgrades posted in between.=A0 The two differ regarding which packages ar= e present, but for those present, they'd seem to be at the same versions. >=20 > One shows this problem quite consistently, the other doesn't show it at a= ll.=A0 It's the newer one, which has a good amount of memory to spare and i= s usually the more reliable these days, that is showing the problem. >=20 > I can recreate the problem at will on the one that shows it by starting X= Win at the command line directly, under xinit, or under startxwin.=A0 But i= f I try to start XWin under gdb, I don't see the problem; see below.=A0 (Th= e page you pointed me to suggests attaching gdb after startup, but that doe= sn't seem reasonable in this case.) >=20 > I notice in the output from starting XWin at the command line there's the= line >=A0 =A0 =A0 =A0 3 [main] XWin 4520 fork: child 5408 - died waiting for dll= loading, errno 11 > I didn't see this output or captured in /var/log/xwin/XWin.0.log when I r= an via xinit or startxwin.=A0 I don't know if that line got generated but l= ost in output redirections, or if this way of starting X is maybe seeing ye= t a different problem.=A0 This line seems similar to that reported by Denis= Beauchemin, Wed, 19 Oct 2011 14:17:54 +0000. Yes, this line is output directly by the cygwin DLL, so you won't see it in= XWin.0.log This output is typical of some other software causing cygwin problems with = fork emulation, see [1] and [2] in the FAQ. > Any suggestions re how else to get the backtrace you desire, or any other= info that might be helpful? You may be able to get something useful using the JIT debugger, by setting = the error_start token in the CYGWIN env var, prior to invoking the command = which crashes, e.g. CYGWIN=3D"error_start=3DC:\cygwin\bin\dumper" CYGWIN=3D"error_start=3DC:\cygwin\bin\gdb" > The below were run within a shell within Emacs running on an X server oth= er than :0.=A0 The behavior looks the same as when running in a Windows CMD= shell, except here the XWin output seems to be printing locally rather tha= n going to XWin.0.log.=A0 The "@@@@@@@"s are hand-edited whiteouts. >=20 > The note below about Zonealarm is "interesting".=A0 No Zonealarm, tho do = have McAfee's firewall enabled. Apparently cygcheck detects ZoneAlarm by looking for the registry key "SYST= EM\\CurrentControlSet\\Services\\vsdatant", or the file "%windir%\\System32= \\vsdatant.sys". > The run under gdb seemed to startup ok; I closed up X after a little whil= e via "Exit..." on the taskbar icon. [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-fork-failures [2] http://cygwin.com/faq-nochunks.html#faq.using.bloda -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/