Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <20010803180442.46438.qmail@web14702.mail.yahoo.com> Date: Fri, 3 Aug 2001 11:04:42 -0700 (PDT) From: Zaphod Box Subject: random stackdumps during long running builds To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii When I'm doing long running builds I get random stackdumps from usually bash.exe and make.exe and sometimes they come from other binaries from /cygwin/bin - this may point the finger to 'cygwin1.dll' as the main culprit since they all share this dll. When i try to read these stackdumps, i don't see much information: e.g. ==>cat bash.exe.stackdump Exception: STATUS_ACCESS_VIOLATION at eip=C213440C ==>make.exe.stackdump Exception: STATUS_ACCESS_VIOLATION at eip=C213474C There is no other content in these stackdumps. Is there an env variable for generating better stackdumps? Or is the only way building my own debug version of cygwin1.dll? I'm running w/ latest version of cygwin (1.3.2-1) on Win2K. The wierd thing is that when i do these builds locally, i usually never see this problem. It is only when i'm remotly building - (logged in via rlogin, rsh, telnet). Is this a known problem and are there any workarounds? Thanks a bunch! Zap __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ -- 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/