Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Paul Derbyshire" <derbyshire AT globalserve DOT net>
To:	cygwin AT cygwin DOT com
Date:	Sun, 28 Jul 2002 07:12:22 -0400
MIME-Version:	1.0
Subject:	Re: Mysterious gdb behavior.
Reply-to:	derbyshire AT globalserve DOT net
Message-ID:	<3D439956.10056.53A4C2DE@localhost>
References:	<3D43020A DOT 30440 DOT 5155C2C9 AT localhost>
In-reply-to:	<1027817663.1910.36.camel@lifelesswks>

On 28 Jul 2002 at 10:54, Robert Collins wrote:

> On Sun, 2002-07-28 at 10:26, Paul Derbyshire wrote:
> > On 27 Jul 2002 at 17:01, Michael A Chase wrote:
> 
> > > Try looking at it with a fixed pitch font.  I suspect he's pointing out
> > > that gdb, like many UNIX programs, doesn't deal well with spaces in file or
> > > directory names.
> > 
> > And why, pray tell, does it have to? The image I was debugging was in 
> > the current directory. It shouldn't care what the path name looks 
> > like.
> 
> It has to because it can't assume that a given image will always be
> accessed by a relative path, and that it won't collide with something in
> the PATH variable.
>  
> > Also, Windows API calls should deal with it just fine. It's a Windows 
> > API call that's failing, according to one of the other posters.
> 
> It's a windows API error code that is being reported. It may or may not
> be a windows API error - it may be unix orientated code doing the wrong
> thing. 
>  
> > Also, if path names with spaces in are problems, then explain why 
> > Cygwin's installer *automatically created* that directory and made it 
> > my home directory? 
> 
> Because we're mean. 

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.

Really, spaces in path names shouldn't bother any part of the system. 
Wherever path names with spaces are handed off to shells or whatever 
they should be quoted, that's all. If path names that went into 
scripts, parameter lists, or whatever were defensively quoted there 
would never be an issue. If it really can't be made to work, then 
perhaps the system should automatically use the short version of 
names with spaces in them? I.e. paulde~1? Windows has handily 
supplied these for all such path names, and they'll be interpreted by 
the underlying filesystem as naming the same place, so...

--
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/

- Raw text -