X-Spam-Check-By: sourceware.org Message-ID: <45A5C74D.8050106@ieee.org> Date: Thu, 11 Jan 2007 00:12:45 -0500 From: Fred Ma User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: "cscope -d" can't find trailer offset if path contains space References: <45A5BE04 DOT 1030301 AT kringlecottage DOT com> In-Reply-To: <45A5BE04.1030301@kringlecottage.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Thanks. Here's some further info: http://groups.google.ca/group/comp.editors/msg/7ffc56871c614f4b Fred Dave & Diane wrote: > > Sorry for the delay - let me take a look at this in more detail. Given > the sleuthing you've done I'll probably have to go back to the cscope > owner at Bell-Labs. > > Will keep you posted. > > Dave > [mlcscope maintainer for cygwin] > > > Fred Ma wrote: > >> 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/