#29 cscope having trouble reading files

closed-wont-fix
nobody
None
5
2011-04-08
2010-09-23
Ken Weinert
No

I *think* this might be related to how our environment is set up, but I'm unclear on whether it's because of links or because of the path components in the link.

First, I run this command: find . -name *.c -o -name *.h > cscope.files

Then I try to run cscope and get a lot of errors like:

cscope: cannot find file INFRASTRUCTURE/thread_engine/include/QueueDef.h

Then: ls -l INFRASTRUCTURE/thread_engine/include/QueueDef.h

INFRASTRUCTURE/thread_engine/include/QueueDef.h -> /source/synergy/data/ccmdb/rxcms/st_root/cache/source/#50/22250

So, does it fail because the file is a link or does it fail because of the # character in the name (somehow interpreted as a comment? )

This is on AIX 5.3 against the most recent bison/flex (which I also just built :)

Discussion

  • cscope generally rejects symlinks. The risk of them causing duplicate symbol entries is just too big.

     
    • status: open --> closed-wont-fix