X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_GJ X-Spam-Check-By: sourceware.org Message-ID: <4F15BC6E.3080506@gmail.com> Date: Tue, 17 Jan 2012 19:22:38 +0100 From: marco atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Another example of intermittent shell failure... References: <17F885176B63DB408864028EADE4D7AAA278FD AT 005-TK5MPN1-002 DOT MGDADSK DOT autodesk DOT com> In-Reply-To: <17F885176B63DB408864028EADE4D7AAA278FD@005-TK5MPN1-002.MGDADSK.autodesk.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 On 1/17/2012 5:10 PM, Paul Breslin wrote: > 0 [main] sh 2272 exception::handle: Exception: STATUS_ACCESS_VIOLATION > 630 [main] sh 2272 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump > 0 [main] sh 3392 exception::handle: Exception: STATUS_ACCESS_VIOLATION > 808 [main] sh 3392 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump > 0 [main] sh 6388 exception::handle: Exception: STATUS_ACCESS_VIOLATION > 727 [main] sh 6388 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump > 0 [main] sh 9316 exception::handle: Exception: STATUS_ACCESS_VIOLATION > 446 [main] sh 9316 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump > 0 [main] sh 1872 exception::handle: Exception: STATUS_ACCESS_VIOLATION > 851 [main] sh 1872 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump > 0 [main] sh 9160 exception::handle: Exception: STATUS_ACCESS_VIOLATION > 424 [main] sh 9160 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump > 0 [main] sh 3784 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x600, errno 11 > /bin/sh: fork: retry: Resource temporarily unavailable fork issues are usually solved with rebaseall, additionally you can also try a recent snapshots http://cygwin.com/snapshots/ -- 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