When you say you "tagged all the files", I assume that means you recursively added "*.*" to the project. How about if you trim that down to just the source files, like "*.cpp;*.h", for example.
I used "*.c; *.cpp; *.cxx; *.h; *.hpp; *.hxx; *.idl; *.inc; *.mk; *.txt". There are not a whole lot of inc, mk and txt files in the projects, but I'm now wondering what SE is doing with those as far as tagging is concerned.
Also, I'm guessing that if you have a 2GB tag file you are probably tagging a lot of stuff that is irrevelant, or in many ways, worse yet, duplicate versions of the same code.
I think I'm still duplicating the SDK files into the project tag file. I'm looking into this right now (I'm rebuilding both tag files).
What programming language are you working with? Is there embedded code (such as assembly embedded in C)?
This is mostly C++ with some plain C involved as well. There's a bit of assembly embedded in C, yes.
You can delete your workspace history by removing vrestore.slk from your SlickEdit configuration directory, or since you are basically working in a default configuration, just go ahead and delete the entire configuration directory and then start from scratch.
I'll try to remove the tag files individually first and will try the "blow everything" approach next. I was hoping SlickEdit would be interested in more information about the crash though so they could fix it.
Hone your project down to what you really need to be working on. You can create several different workspaces and easily switch between them if you need to work on different versions of the code or different branches of the source tree.
There are some cross references between the various sub-projects and I was hopping I could get symbol look up and autocompletion working throughout the whole source tree. Will I get that if I break things down into smaller projects/workspaces?
For large projects what do people usually do: create multiple projects inside the same workspace; or create various workspaces with a single project inside each one; or perhaps something in between?
Finally, could you create a mini-dump the next time you get the crash? It is very easy to do by simply attaching to SlickEdit with Visual Studio.
I can currently re-create the crash at will. My problem with creating a mini-dump is what it will contain. I guessing it will probably contain information about our projects and I'm pretty sure my employer would not be happy about that. Is there anything else I can provide?