User forums > Using Code::Blocks

codecompletion plugin will eat 100% CPU usage

<< < (2/2)

ollydbg:

--- Quote ---I tried version from svn 8598 to 8628
wxWidgets 2.9.4
--- End quote ---
So, you build C::B against wx2.9.4? Or did you just use some pre-build binaries?
It looks like the CC parser goes to an endless loop, but I can't reproduce this. (I'm under WinXP, no Linux at hand).
Can you try to debug C::B under C::B(If you can build C::B, I believe you can debug it), and hit the pause key when you see Codecompletion hangs, and see where is the infinite loop.

MortenMacFly:
Also, what happens if you use  an "official" (i.e. non-self-built) version?

kipade:
Maybe the problem is not due to CB or WX.
Because I use the same version of WX and CB source code, it works find on other OS. I tried on Ubuntu 10.04 and LFS 7.7.
I think there is something went worth under my Slackware, but Im not sure which features used by codecompletion trap into this hole.
Thanks, all

kipade:
However, I still hope someone would like to help me to resovle this problem under Slackware.

davec55:
I have the same problem and traced it to the '/usr/include/seamonkey/' directory which has 3 soft links to itself
i.e
 nss -> ./
 plugin -> ./
 xpcom -> ./

I have resolved the problem by deleting these links, but someone who knows how the codecompletion directory transversal works can perhaps detect these situations and prevent these from causing continuous loops within the thread.

Navigation

[0] Message Index

[*] Previous page