X-Spam-Check-By:	sourceware.org
Message-ID:	<b4376ea40701031356p79d37499k12f1d97b01188aeb@mail.gmail.com>
Date:	Wed, 3 Jan 2007 16:56:09 -0500
From:	"Fred Ma" <FredMa AT ieee DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Re: "cscope -d" can't find trailer offset if path contains space (was: vim mlcscope interface issues)
In-Reply-To:	<b4376ea40701031354q5adc519eg1d672c800fa85ef7@mail.gmail.com>
MIME-Version:	1.0
References:	<b4376ea40701031354q5adc519eg1d672c800fa85ef7 AT mail DOT gmail DOT com>
X-Google-Sender-Auth:	a19e3a0d85c50f9b
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Bug fix request submitted for cscope via sourceforge:

This problem arose when using vim, but also appears when using "cscope
-d".  I get the error "cannot read trailer offset from file
cscope.out".  I browsed build.c to find that it is caused when reading
in a single number with fscanf.  To see what could be confusing
fscanf, I found the context of the "trailer offset" from
http://www1.bell-labs.com/project/wwexptools/cscope/cscope.html, which
shows that the number to be read occupies a single line along with
other space-delimited data, including the specification of the current
directory.  The space delimiting will get messed up if the current
directory contains spaces, which is often the case in Windows and
Cygwin (though it can also be the case in *nix).  P.S.: It also
happens with mlcscope.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -