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: Sat, 3 Aug 2002 00:09:58 -0400
MIME-Version: 1.0
Subject: Re: thread about Directory names containing spaces and G
Reply-to: derbyshire AT globalserve DOT net
Message-ID: <3D4B1F56.3280.710CC70C@localhost>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body


On 2 Aug 2002 at 10:37, John Vincent wrote:

> 1. try copying the executable to a directory with no spaces in the
> path, and then try gdb to see if this makes a difference.

Predictably, it works.

> If the same problem remains after each step, I'd say that spaces
> in the path were not the issue, and then another hypothesis will
> need to be investigated.

It doesn't remain after step 1. This is consistent with the other 
evidence that the executable itself is not the problem, and with the 
previous behavior of gdb with the executables in my system.



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