"cscope -d" can't find trailer offset if path contains space

[Dave & Diane]

Hi Fred,

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


-- 

Diane & Dave
http://www.velvetstarbears.com/  http://www.kringlecottage.com/
Fortune: The difference between America and England is that the
English think 100 miles is a long distance and the Americans
think 100 years is a long time.


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