Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
New code completion remarks/issues
mmkider:
--- Quote from: jens on September 28, 2009, 09:16:15 am ---I can more or less confirm this crash on linux.
It does not crash, but it hangs and eats 100 % of one of my CPU's.
Latest svn-source.
I will look into it.
--- End quote ---
Cool. :D
I get 100 % of one of my CPU's too, and my codeblocks can not respond to any key.
blueshake:
--- Quote ---This bug is fixed by this patch
--- End quote ---
does it work for codes like these?
--- Code: ---#include <iostream>
using namespace std;
struct qq
{
int x;
int y;
};
struct qq tt;
struct qq& xx = tt;
xx.
int main()
{
cout << "Hello world!" << endl;
return 0;
}
--- End code ---
EDIT:
And the issue in this thread seems not solved yet.http://forums.codeblocks.org/index.php/topic,10966.msg74954.html#msg74954
blueshake:
--- Quote ---I get 100 % of one of my CPU's too, and my codeblocks can not respond to any key.
--- End quote ---
I have this issue too.The programe hang,but 50% of CPU used.
EDIT:
It seems that (x) tip cause this.
Jenna:
--- Quote from: mmkider on September 28, 2009, 09:19:10 am ---
--- Quote from: jens on September 28, 2009, 09:16:15 am ---I can more or less confirm this crash on linux.
It does not crash, but it hangs and eats 100 % of one of my CPU's.
Latest svn-source.
I will look into it.
--- End quote ---
Cool. :D
I get 100 % of one of my CPU's too, and my codeblocks can not respond to any key.
--- End quote ---
Should be fixed in svn r5825.
By the way:
we should have a look at all occurrences of MoveToNextChar(), because testing for EOF does not make sense after this function. At EOF it returns false and sets the token-index to bufferlen (this was the cause for the endless-loop in this case).
Jenna:
--- Quote from: blueshake on September 28, 2009, 10:18:25 am ---
--- Quote ---I get 100 % of one of my CPU's too, and my codeblocks can not respond to any key.
--- End quote ---
I have this issue too.The programe hang,but 50% of CPU used.
EDIT:
It seems that (x) tip cause this.
--- End quote ---
That's partly correct, the issue does not occur, if I cancel the (x)-tip with escape, but it hangs in in SkipToOneOfChars() because we never reach EOF and so never break out of the while-loop.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version