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: Sun, 28 Jul 2002 19:37:58 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Mysterious gdb behavior. Message-ID: <20020728233758.GB19054@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3D43020A DOT 30440 DOT 5155C2C9 AT localhost> <3D439956 DOT 10056 DOT 53A4C2DE AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D439956.10056.53A4C2DE@localhost> User-Agent: Mutt/1.3.23.1i On Sun, Jul 28, 2002 at 07:12:22AM -0400, Paul Derbyshire wrote: >OK. Is anyone going to actually suggest a solution here? And don't >say "rename the directory", I don't imagine renaming the home >directory to something other than your user name is going to do >anything but cause more trouble. Have you actually tried this in a directory without spaces in it? I don't recall seeing that experiment. Two things that I would suggest are 1) Try explictly specifying the path and extension when debugging i.e., "gdb -nw ./foo.exe". 2) Try the test version of gdb, available when you select "Exp" in the package installation screen when running setup.exe. I just tried this version in a directory with spaces and it seemed to work ok. This version of gdb does have some reported occasional memory corruption problems but I haven't noticed them personally. That may be because I rarely use the GUI version of gdb. 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/