Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <20030113075922.A16536@CS.CMU.EDU> Date: Mon, 13 Jan 2003 07:59:22 -0500 From: Bhiksha Raj To: cygwin AT cygwin DOT com Subject: Re: BSOD on cygwin References: <20030112183440 DOT A13001 AT CS DOT CMU DOT EDU> <4 DOT 3 DOT 1 DOT 2 DOT 20030112192405 DOT 036bec98 AT pop DOT rcn DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <4.3.1.2.20030112192405.036bec98@pop.rcn.com>; from Larry Hall (RFK Partners, Inc) on Sun, Jan 12, 2003 at 07:35:44PM -0500 Im not sure what happened, but my problem went away. I do not have VPN or an antivirus program running - I turned those off due to some problems with other software earlier. No firewall software either - I have an external DLink firewall. For the record, here's what I did that seemed to fix things: 1. I reinstalled cygwin 1.3.8.1. "cygcheck" ran once after the reinstall, but failed again on subsequent runs. The machine still crashed when I tried to "./configure" guile. 2. The configure script was dying at a "uniq". I tried running uniq on a file, from the command line. It crashed the window (not the machine), with a windows popup message about some dll. I didnt note it down (unfortuntely). 3. I restarted another cygwin window and reran uniq on the same file. This time uniq went through. 4. I reran configure (note that I havent *changed* anything after the earlier run, when the machine crashed). It went through cleanly. 5. I double checked. 'cygcheck' also returns proper results. Since I did not actively modify anything, Im mystified why things went through after I ran uniq on the command line. Thanks, Bhiksha On Sun, Jan 12, 2003 at 07:35:44PM -0500, Larry Hall (RFK Partners, Inc) wrote: > Perhaps someone else running Win98 will be able to confirm or deny > the problems you're seeing. I'm guessing that others will only be > able to 'deny'. As mentioned, BSOD is an O/S issue/bug, which means > it's at least difficult to resolve in application software and is > certainly much better resolved in the O/S itself (or quite possibly > software drivers). Certainly in the case that the problem is caused > by drivers (and AV software uses these too), the problem software is > not necessarily installed on a 'typical' Win 98 machine, which is why > I said I expect others won't be able to confirm your results. I'd > highly recommend following Igor's suggestions. The fact that you > can't get cygcheck to run correctly for you again makes me highly > suspicious that something on your system other than Cygwin is actually > causing your problem. In my opinion, you're more likely to find the > source of your problem by looking outside of Cygwin. > > > > Larry Hall lhall AT rfk DOT com > RFK Partners, Inc. http://www.rfk.com > 838 Washington Street (508) 893-9779 - RFK Office > Holliston, MA 01746 (508) 893-9889 - FAX > > > At 06:34 PM 1/12/2003, Bhiksha Raj wrote: > >Hi, > > > >First I must apologize for my multiple posts earlier. > >I wasnt sure if the first one had gone through, since I never > >got a copy myself. So I figured Id messed up and posted again. > > > >Anyway, > >the problem (as I mentioned earlier) is that on my windows 98 > >machine, with the latest cygwin, I get a blue screen of death > >when I try to run "configure --disable-shared" on guile-1.4.1. > >(Im using 1.4.1 because Im tyring to compile TeXmacs). > > > >Ive since dug around a bit, crashed my machine a hunded times, > >and collected logs. I found that the configure script dies > >on line 4791, at a line that goes > >"if sort conftest.nm|uniq > conftest.ntM;then" > > > >I get an empty conftest.nmT and the machine dies. > >I tried running the same command from command line. The first time > >I ran it, my cygwin window froze (although my machine didnt die), > >but thereafter Ive been able to run it from command line. > >However, running the configure script kills the machine at the > >uniq again. > > > >Im attaching the configure script, the config.log, and the > >conftest.nm files (the conftest.nmT file I get is empty). > >I hope this is not bad practice, but I figure they would help > >find the problem. > >The tail of the config.log file should indicate where exactly > >my machine dies (every time!). > >Also, as per Igor Pechtchanski's suggestion, I ran a cygcheck -s -v -r and > >am attaching the output. > > > >Curiously, cygcheck -s -v -r gave me output the first time I > >ran it. Afterwards, running the command simply gives me no output > >at all - it simply runs silently and comes back. Im not sure why > >this is so - I was pretty sure it was supposed to repeat the > >information everytime I ran it. I hope this doesnt indicate a > >bug with my setup. > > > >Many thanks for any and all help in this issue. > > > >Regards, > >Bhiksha > >bhiksha AT merl DOT com > > > > > >On Sun, Jan 12, 2003 at 10:40:48AM -0500, Igor Pechtchanski wrote: > > > On Sun, 12 Jan 2003, Igor Pechtchanski wrote: > > > > > > > On Sat, 11 Jan 2003, Bhiksha Raj wrote: > > > > > > > > > Hi All, > > > > > > > > > > I hope this is not the wrong forum for this: > > > > > > > > > > Im trying to install TeXmacs on my win98+cygwin laptop. > > > > > First I installed the binaries for guile from the cygwin setup > > > > > (I have XFree and Tex and all associated libs already) > > > > > downloaded TeXmacs sources, ran ./configure and then > > > > > gave a "make". > > > > > I got the blue screen of death (BSD). > > > > > After iterating through several BSDs, I hunted on the web > > > > > and found a site that said that static linkages were a problem with > > > > > the latest guile and that I must install guile 1.4.1. So I uninstalled > > > > > guile, > > > > > downloaded the sources for guile 1.4.1, untarred them and > > > > > ran > > > > > ./configure --disable-shared > > > > > > > > > > It runs through several checks, but never completes - insted it > > > > > gives me at some point it simply gives me the blue screen of death. > > > > > This time around Im not even getting past configure. > > > > > > > > > > Im not sure what to do now. > > > > > Any advice at all would be greatly appreciated. > > > > > > > > > > Much thanks > > > > > Bhiksha > > > > > bhiksha AT merl DOT com > > > > > > > > Bhiksha, > > > > > > > > This is a forum for all problems with Cygwin, so your question fits in > > > > nicely. To answer it, Cygwin never *causes* a BSOD. It may expose or > > > > trigger a bug in Windows or some process running with system privileges > > > > (antivirus programs have been blamed a lot), but Cygwin itself doesn't > > > > have enough access to the low-level OS to be able to cause a BSOD. > > > > > > > > Try turning off your antivirus program(s) and see if it makes the BSOD go > > > > away. Another possibility is firewall or VPN software. The output of > > > > 'cygcheck -s -v -r' as a non-inline uncompressed text *attachment* > > > > wouldn't hurt, either (as indicated in ). > > > > Igor > > > > P.S. I'm sure you'll get more and better responses on Monday. > > > > > > Whoops! Fingers striving to be independent from the brain... Make the > > > above link (also at the bottom of every > > > message). > > > Igor > > > -- > > > http://cs.nyu.edu/~pechtcha/ > > > |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu > > > ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com > > > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski > > > '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! > > > > > > Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! > > > -- /usr/games/fortune > > > > > > > > > -- > > > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > Bug reporting: http://cygwin.com/bugs.html > > > Documentation: http://cygwin.com/docs.html > > > FAQ: http://cygwin.com/faq/ > > > > > > > > > > > > >-- > >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > >Bug reporting: http://cygwin.com/bugs.html > >Documentation: http://cygwin.com/docs.html > >FAQ: http://cygwin.com/faq/ > > > ################################################################# > ################################################################# > ################################################################# > ##### > ##### > ##### > ################################################################# > ################################################################# > ################################################################# > > ################################################################# > ################################################################# > ################################################################# > ##### > ##### > ##### > ################################################################# > ################################################################# > ################################################################# > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/