| T O P I C R E V I E W |
| Michal Puczynski |
Posted - Jun 20 2007 : 05:26:26 AM
After installing 1557 I run into problem when editing and compiling code in the same time. In order to reproduce, compiler must run in background, then some edit operations shall be performed on the code. I am not sure about what edit operations cause it, but most likely selection and copy/paste are the one.
The devenv hangs. CPU is at 100% and stack of
most working thread is (not the main thread):
FEACP!GetMultiByteString+0x75
FEACP!GetMultiByteIdInBuffer+0xf
FEACP!GetMultiByteId+0x24
FEACP!GetTokenFromCurrentChar+0x4a1
FEACP!TokenStreamStack::getToken+0x1b
FEACP!TokenStream::captureTokenStream+0x16d
FEACP!TokenStream::captureInjectedText+0xf9
FEACP!NCBBrowse_t::LoadFunction+0x15a
FEACP!NCBBrowse_t::LoadSymbol+0x9c9
FEACP!ParseQname+0x8e
FEACP!LexerResolveIdentifierWorker+0x45
FEACP!LexerResolveIdentifier+0x1e
FEACP!yylex+0x391
FEACP!PrimaryParser::Parse+0x3738
|
| 7 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jun 25 2007 : 1:34:35 PM
To be honest I have no idea. Moving from 1555 to 1557 should not have broken anything, but obviously it has.
Can you try the zero length read only NCB file and see if this makes any difference?
When you are seeing this problem are the files you are editing being compiled? Or are they not part of the compilation?
I am wondering if somehow VA and the IDE are both trying to "grab" the same code file at the same time. This is a very bad theory, but I am not sure what else might be going on.
Do you have any other plugins installed? |
| Michal Puczynski |
Posted - Jun 25 2007 : 10:38:49 AM
How does it link to 1555->1557 change? When I get back to 1555 problem disappears....
Maybe all the problems I have recently reported have something common with "Get content from default IntelliSense". I mean deadlocks, crashing and 'search in files' problem.... |
| feline |
Posted - Jun 25 2007 : 07:20:02 AM
That makes some sense, certainly it may be worth a try. I do know a corrupt NCB file will cause VS2003 to crash when you try to load the solution.
See here for some details on NCB files and disabling the IDE's intellisense:
http://docs.wholetomato.com?W133 |
| Erik Olofsson |
Posted - Jun 24 2007 : 4:36:50 PM
FEACP in the callstack is a reference to the default c++ intellisense. Ever since Visual Studio 2002 it has been many a programmers habit to rename feacp.dll to stop the default intellisense from working and solve a lot of hickups. With Visual Assist there is not much need for it anyway. You could also try to delete the solution ncb file. |
| feline |
Posted - Jun 21 2007 : 10:56:25 AM
The read only files was mainly aimed at C#
Are the files you are editing going to be compiled? Or are you compiling one project in your solution and editing code in a different solution?
Ignoring the deadlock for a second I would expect editing while compiling to be a bad idea, simply because the compiler might try to compile the file you are editing while it is in an invalid state. |
| Michal Puczynski |
Posted - Jun 21 2007 : 09:00:57 AM
Hello. It is VC++2003. Was (usually is) one instance, and no C#, only C++.
The switch you are referring to is also present in 2003 and it is enabled
in my case. However, I hardly believe I had any read-only file open. |
| feline |
Posted - Jun 20 2007 : 07:03:01 AM
Which IDE and programming language are you using?
Are you running more than one instance of the IDE at a time?
VS2005 likes to mark all C# code as read only once the program is actually running.
If you are using VS2005 do you have:
IDE tools menu -> Options -> Environment -> Documents -> Allow editing of read-only files; warn when attempt to save
turned on or off? |
