Description of problem: There are numerous cscope.* directories in /tmp Version-Release number of selected component (if applicable): cscope-15.5-15.4.fc7 How reproducible: Always, I'd guess. Steps to Reproduce: 1. cscope -bRv in $DIRECTORY 2. $EDITOR 3. repeat step 1 and 2 as one normally would Actual results: $ ls -1td /tmp/cscope.* | wc -l 184 $ ps uax | grep cscope peb 3697 0.0 0.0 4044 676 pts/9 S+ 11:54 0:00 grep cscope peb 15058 0.0 0.1 3068 1364 pts/7 S+ Apr21 0:00 /usr/bin/cscope -dl -f cscope.out peb 23171 0.0 0.1 2960 1240 pts/2 S+ Apr19 0:00 /usr/bin/cscope -dl -f cscope.out peb 25924 0.0 0.1 3068 1360 pts/6 S+ Apr20 0:00 /usr/bin/cscope -dl -f cscope.out Expected results: I'd say: $ ls -1td /tmp/cscope.* | wc -l 3 Additional info: 0) Note that some directories date from before the last boot (i.e. they are persistent). Also note that most directories are empty. Only a few got cscope.[12] files in them. 1) There is a /tmp/cscope.15058, /tmp/cscope.23171 and a /tmp/cscope.25924 directory in /tmp, so the format seems to be "/tmp/cscope.$pid". 2) $EDITOR=vim. I've seen cscope (or vim) complain every now and then (when starting vim). That might be related. When that happens again I'll try to add a comment with the error message.
I'm quite sure that this has been caused by vim and that this isn't a cscope bug. I'll build a new vim package for F-8 with a fix for this issue.
Thanks. This must be a duplicate of bug # 435761. I'll close this one. *** This bug has been marked as a duplicate of 435761 ***