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 Date: Mon, 29 Jul 2002 11:37:28 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Mysterious gdb behavior Message-ID: <20020729153728.GC16707@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <30C9E24891FFD411B68A009027724CB702C04D0B AT eg-002-015 DOT eglin DOT af DOT mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <30C9E24891FFD411B68A009027724CB702C04D0B@eg-002-015.eglin.af.mil> User-Agent: Mutt/1.3.23.1i On Mon, Jul 29, 2002 at 08:09:39AM -0500, Keen Wayne A Contr AFRL/MNGG wrote: >To add a bit of related trivia to this wonderful thread, I find it >interesting that the current relase of Dev-C++ is suffering with a >similar problem. If you set Dev up in the "Program Files" directory, >it has crash and burn type problems due to the spaces in the directory >name as well. Hmm. This is reaching urban myth proportions. AFAIK, gdb works fine with a path with spaces in it. There is no indication to the contrary, so far. This has been a very strange thread. cgf -- 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/