Author Topic: Tag File Issues  (Read 2184 times)

TKasparek

  • Senior Community Member
  • Posts: 246
  • Hero Points: 29
Tag File Issues
« on: May 15, 2015, 09:55:09 PM »
Anybody else still having other tag file issues? I use wildcards for my projects and I'm regularly having to refresh the project or rebuild the tag file in order to get all references (no files have changed). I've also recently started hitting (once or twice a day) SE not recognizing the actual implementation of class functions. I can navigate to the proto and all other references but I have to do a search to get to the function.

~Tom

Quote
SlickEdit Pro 2014 (v19.0.2.5 64-bit)

Serial number: WMX110555
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\19\slickedit.lic

Build Date: April 10, 2015
Emulation: CUA

OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 16% Load, 5391MB/32712MB Physical, 6072MB/34710MB Page File, 1207MB/8388607MB Virtual
Shell Information: C:\Windows\system32\cmd.exe /q
Screen Size: 1920 x 1080, 1920 x 1080, 1920 x 1080

Project Type: Cpp
Language: .cpp (C/C++)
Encoding: Automatic

Installation Directory: C:\Program Files\SlickEdit Pro 19.0.2\ (non-removable drive,NTFS,298982MB free)
Configuration Directory: C:\Users\test41l\Documents\My SlickEdit Config\19.0.2\ (non-removable drive,NTFS,298982MB free)
Spill File: C:\Users\test41l\AppData\Local\Temp\$slk.3872 (non-removable drive,NTFS,298982MB free)

Hotfixes:
C:\Users\test41l\Documents\My SlickEdit Config\19.0.2\hotfixes\hotfix_se1902_tools_tag_files.zip (Revision: 1)



Dennis

  • Senior Community Member
  • Posts: 3961
  • Hero Points: 517
Re: Tag File Issues
« Reply #1 on: May 16, 2015, 12:32:29 AM »
If you're willing to work with me, we can try to debug this.

1) Rebuild your workspace tag file from scratch.  (Project > Retag Workspace...)
2) Then exit the editor and make a backup of that workspace tag file.
3) Now turn on the following macro variable to enable logging (Macro > Set Variable... > def_tagging_logging=1).  As soon as you encounter one of the problems, note the file's involved, and capture <config>/logs/tagging.log.
4) Exit the editor again and make a copy of the workspace tag file in it's current state (where you are getting failures).
5) Turn def_tagging_logging back off and rebuild your tag file.

Send me the original tag file, the current tag file, tagging.log, and notes about what files and symbols were involved with the failed searches.  I can look over all this data and see if I can identify the problem.  The caveat is that I need all the data, otherwise, I won't be able to determine what is missing from the tag file when it is failing.