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: <42FC1AE2.4030406@byu.net> Date: Thu, 11 Aug 2005 21:43:30 -0600 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: Matthew Carroll Subject: Re: bash.exe.stackdump References: <20050726181610 DOT XEBJ3347 DOT ibm60aec DOT bellsouth DOT net AT mail DOT bellsouth DOT net> <42E778CA DOT 4060409 AT byu DOT net> In-Reply-To: <42E778CA.4060409@byu.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Eric Blake on 7/27/2005 6:06 AM: >>> OS: cygwin >>>Bash Version: 3.0 >>>Patch Level: 16 >>>Release Status: release >>> >>>Description: >>> Below are the contents of the "bash.exe.stackdump" > > > And what were you doing at the time of the crash? Any formula for > reproducing the error? Otherwise this is a useless bug report. A recent cygwin bug was fixed where fork() with a huge (> 1 meg) command line would corrupt memory, then the child bash process would segfault as a result. Since you have not provided any more details as to what caused your crash, I will have to assume that using a fixed cygwin probably corrects your problem with no change to bash. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC/Bri84KuGfSFAYARAtNcAKCdr3A9QmRJJLpBbdX9G5FM3AL4/gCdGvOo pkidsODCqqz9eBR2IxQwUgo= =3zxr -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/