User forums > Nightly builds

The 25 september 2010 build (6634) CODECOMPLETION BRANCH version is out.

<< < (8/24) > >>

Jenna:

--- Quote from: ollydbg on October 03, 2010, 04:22:35 pm ---
--- Quote from: Loaden on October 03, 2010, 04:14:27 pm ---Thanks! This code lead CB endless loop.
I will fix it soon.

--- Code: ---#define AAA(x) BBB(x)
#define BBB(y) AAA(y)

#if AAA(1) && BBB(2)
void fly();
#else
void good();
#endif
--- End code ---

--- End quote ---

But the code above does not compile. :D

--- End quote ---

The kernel code surely does not compile also (all files added to a C::B project without running any configuration-scripts and without using makefiles), but it leads to an endless loop when parsing the sources and that should (of course) not happen, even if the code has errors.

ollydbg:

--- Quote from: jens on October 03, 2010, 04:34:37 pm ---The kernel code surely does not compile also (all files added to a C::B project without running any configuration-scripts and without using makefiles), but it leads to an endless loop when parsing the sources and that should (of course) not happen, even if the code has errors.

--- End quote ---


--- Quote from: Loaden on October 03, 2010, 04:30:05 pm ---But we still have to avoid all possible infinite loop. :lol:

--- End quote ---

Yes, 100% agree.
Maybe, we could limit the macro expansion level to avoid the recursive infinite loop.
Eg, once a macro definition is used to do macro expansion, it will never be used again in deeper level expansion.

Loaden:

--- Quote from: ollydbg on October 03, 2010, 04:40:32 pm ---Maybe, we could limit the macro expansion level to avoid the recursive infinite loop.

--- End quote ---
Agreed! This is a good idea. :D

Loaden:

--- Quote from: jens on October 03, 2010, 04:34:37 pm ---The kernel code surely does not compile also (all files added to a C::B project without running any configuration-scripts and without using makefiles), but it leads to an endless loop when parsing the sources and that should (of course) not happen, even if the code has errors.

--- End quote ---
Hi, Jens, Please trying this patch?

Jenna:

--- Quote from: Loaden on October 03, 2010, 05:30:52 pm ---
--- Quote from: jens on October 03, 2010, 04:34:37 pm ---The kernel code surely does not compile also (all files added to a C::B project without running any configuration-scripts and without using makefiles), but it leads to an endless loop when parsing the sources and that should (of course) not happen, even if the code has errors.

--- End quote ---
Hi, Jens, Please trying this patch?

--- End quote ---

The endless loops do no longer occur.

Parsing takes a little more than 28 minutes, that's very long, but I get more than 1 million tokens.
One problem is the amount of memory used (more than 2 GB).
And it seems parsing is not correct, I get some strange tokens in symbol browser (see the attached picture).
I am currently uploading a 7z-file, that contains the tokens tree and the outher lists from cc debug tool.
That will take some time (just ISDN here), because it's about 18 MB (105 MB tokens tree).

Another issue (not related to this), is that the symboslbrowser stays empty, if the project is opened without any shown editor.
After opening any file the symbols-browser gets filled.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version