public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: "Fred Ma" <FredMa@ieee.org> To: cygwin-xfree@cygwin.com Subject: "cscope -d" can't find trailer offset if path contains space (was: vim mlcscope interface issues) Date: Wed, 03 Jan 2007 21:54:00 -0000 [thread overview] Message-ID: <b4376ea40701031354q5adc519eg1d672c800fa85ef7@mail.gmail.com> (raw) Bug fix requested 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://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next reply other threads:[~2007-01-03 21:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-03 21:54 Fred Ma [this message] 2007-01-03 21:55 ` Fred Ma 2012-04-17 7:55 Schwarz, Konrad 2012-04-17 8:07 ` marco atzeri 2012-04-17 23:15 ` Jim Reisert AD1C 2012-04-18 4:44 ` Vivek Agarwal
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=b4376ea40701031354q5adc519eg1d672c800fa85ef7@mail.gmail.com \ --to=fredma@ieee.org \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).