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: Fri, 2 Aug 2002 23:44:30 -0400
MIME-Version: 1.0
Subject: Re: thread about Directory names containing spaces and G
Reply-to: derbyshire AT globalserve DOT net
Message-ID: <3D4B195E.23583.70F5767B@localhost>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

On 2 Aug 2002 at 5:55, Dockeen wrote:

> One other data point which might be helpful in debugging
> would be to provide the results of
> 
> gcc -v
> which gcc
> which gdb
> 
> Make sure you run these commands in the same shell you used
> to compile your executable.  This should allow running to
> ground of any issues about which compiler was used...

I thought they were already sufficiently run to ground but:
-- As reported previously, the version reported is 2.95.x, while at a
   DOS prompt it's 3.x.
-- which gcc, which gdb -- /usr/bin/foo.
-- Copying the "hw" test executable to a directory without spaces in
   the pathname allows debugging. This is the same exact executable
   that was choking it, without a byte changed. Only the path is
   different. Therefore the path is the cause.


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