Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

Constant hang with 7763

(1/3) > >>

ironhead:
I've updated to the latest svn version (7763 as of this post) and it constantly hangs when CC is supposed to kick in (i.e. on the 3rd character).  I've done a '--debug-log-to-file' but since I have to kill the codeblocks.exe process, it's a truncated file (at 4096 bytes).  Is this a known issue?

I'm running codeblocks self compiled using MinGW gcc 4.6.2 on Windows XP Pro SP3.

ollydbg:
I can confirm it hangs (Even in a very simple tiny code snippet)

I try to find the reason, but no success.

1, I debug it under gdb, and when it hangs, I pause the gdb, and check all the threads and call stack, I only find one:

One thread is halted in:
[debug]#5  0x65ed5270 in CodeCompletion::CodeComplete (this=0x3b9f458) at E:\code\cb\cb_trunk\src\plugins\codecompletion\codecompletion.cpp:968
Here is a cs enter, so the main GUI hangs.
The other thread has no useful information.

2, I try to enable the "#define CC_ENABLE_LOCKER_TRACK", and add '--debug-log-to-file', but when viewing the debug log file, I can't find anything wrong, the last message is:

--- Code: ---....
s_TokensTreeCritical.Enter() : ExpandItem(), E:\code\cb\cb_trunk\src\plugins\codecompletion\classbrowserbuilderthread.cpp, 1040
s_TokensTreeCritical.Entered() : ExpandItem(), E:\code\cb\cb_trunk\src\plugins\codecompletion\classbrowserbuilderthread.cpp, 1040
s_TokensTreeCritical.Leave() : ExpandItem(), E:\code\cb\cb_trunk\src\plugins\codecompletion\classbrowserbuilderthre

--- End code ---

The ugly thing is: The main GUI hangs, so the cc_logger does not work anymore. :(

Jenna:
It does not hang here, neither on linux nor win7.

Did you do a real clean rebuild. I mean manually cleaned (devel, output, .objs and include/*.gch) to be absolutely sure no artefacts of a prior build are left ?
Or a fresh and clean svn checkout ?

MortenMacFly:

--- Quote from: jens on February 02, 2012, 06:30:59 am ---It does not hang here, neither on linux nor win7.

--- End quote ---
Not here, too. You can try to add a #define CC_ENABLE_LOCKER_ASSERT in the compiler options of the CC target and re-compile this plugin. If it still hangs, it should not be the lockers.

ollydbg:
I did a clean build. The strange thing is:
if I run the new build c::b under c::b, then the new c::b will hang.
If I run the new c::b separately, it does not hang.
EDIT both cases hang.

Navigation

[0] Message Index

[#] Next page