X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sat, 25 Jul 2009 10:28:44 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: bug triggered by long file names in cygwin 1.7.0-52 Message-ID: <20090725082844.GQ18621@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <813D52B15F7D419D8A6C07867641825C AT somerville> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <813D52B15F7D419D8A6C07867641825C@somerville> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Jul 24 17:21, Dan Stratila wrote: > After thinking about this for a bit, I realized that the problem is related > to the fact that bash sets the window title to the current path. When I > change PS1 to only place the basename of the current path in the window > title, the crash no longer happens: That was *the* hint. In case the path got longer than 256 chars, an erroneous statement overwrote parts of the stack. I fixed that in CVS. Thanks for the report, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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