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

Code Completion & Workspace

<< < (6/7) > >>

MortenMacFly:

--- Quote from: ollydbg on May 13, 2011, 08:14:57 am ---the attachment zip file has not cpp files in it? did you forget attach them?

--- End quote ---
No, that is on purpose. It's enough, if CC tries to parse the "up-front" headers (wx in this case).

ollydbg:
Here is the log in my PC:

--- Quote ---Loading workspace "F:\cb\test_code\Demo\Demo.workspace"
Loading project file...
Parsing project file...
Loading target default
Loading project files...
1 files loaded
Done loading project in 31ms
Project's base path: F:\cb\test_code\Demo\
Project's common toplevel path: F:\cb\test_code\Demo\
Loading project file...
Parsing project file...
Loading target default
Loading project files...
1 files loaded
Done loading project in 0ms
Project's base path: F:\cb\test_code\Demo\
Project's common toplevel path: F:\cb\test_code\Demo\
Caching GCC dir: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\c++
Caching GCC dir: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\c++\i686-pc-mingw32
Caching GCC dir: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\c++\backward
Caching GCC dir: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\include
Caching GCC dir: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include
Caching GCC dir: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include-fixed
Caching GCC dir: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\i686-pc-mingw32\include
Passing list of files to batch-parser.
Header to parse up-front: 'D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\c++\cstddef'
Header to parse up-front: 'D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\i686-pc-mingw32\include\w32api.h'
Header to parse up-front: 'D:\code\wxWidgets-2.8.12\include\wx\defs.h'
Header to parse up-front: 'D:\code\wxWidgets-2.8.12\include\wx\dlimpexp.h'
Header to parse up-front: 'D:\code\wxWidgets-2.8.12\include\wx\toplevel.h'
Add up-front parsing 5 file(s) for project 'Demo'...
Add batch-parsing 1 file(s) for project 'Demo'...
Create new parser for project 'Demo'
Starting batch parsing for project 'Demo'...
Project 'Demo' parsing stage done (141 total parsed files, 12725 tokens in 0 minute(s), 12.562 seconds).
Updating class browser...
Class browser updated.
Add project (Demo (static)) to parser
Get Headers: D:\code\wxWidgets-2.8.12\include\ , 688
Get Headers: D:\code\wxWidgets-2.8.12\lib\gcc_dll\mswu\ , 2
Get Headers: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\c++\ , 611
Get Headers: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\c++\i686-pc-mingw32\ , 23
Get Headers: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\c++\backward\ , 8
Get Headers: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\include\ , 5
Get Headers: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include\ , 39
Get Headers: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\lib\gcc\i686-pc-mingw32\4.5.4\include-fixed\ , 3
Get Headers: D:\code\mingw_gcc4.5.4.20110428_static_win32\MinGW\i686-pc-mingw32\include\ , 1231
Get the system header file path: 9


--- End quote ---

looks like there should be a log saying that, but in-fact no such log message, that's strange.

--- Quote ---Project 'Demo static' parsing stage done.....
--- End quote ---

edit: the CPU usage is quite low (<5%), it seems CC was not in a infinite loop.

MortenMacFly:

--- Quote from: ollydbg on May 13, 2011, 08:27:22 am ---edit: the CPU usage is quite low (<5%), it seems CC was not in a infinite loop.

--- End quote ---
It's not an "infinite loop" in a sense that it eats CPU. But it never returns and so all CC actions will report "parser still parsing files" forever.

IMHO the parser fails silently with an error and this is not handeled correctly.

ollydbg:

--- Quote ---It's not an "infinite loop" in a sense that it eats CPU. But it never returns and so all CC actions will report "parser still parsing files" forever.

IMHO the parser fails silently with an error and this is not handeled correctly.
--- End quote ---
Yes, I think I will take some time to trace the bug. (not right now :D) I suspect that when batch parsing the second project, no parserthread object was created(all the necessary files were already parsed in the first project) and no files were put into the thread pool, so maybe the "End of batch parse Event" never triggered. :D

Loaden:
The BUG maybe related with memory pool.
Please trying REV7122: "CC: Disable memory pool again, avoid possible crash".

Navigation

[0] Message Index

[#] Next page

[*] Previous page