User forums > Nightly builds
The 27 October 2014 build (10016) is out.
ollydbg:
--- Quote from: pluto on November 03, 2014, 12:43:47 am ---1) The Code Completion option "display info when hovering mouse over a token in the editor" is always active.
Even when uncheckd, it shows a tooltip.
--- End quote ---
I can confirm it, please report it in Sourceforge, thanks.
BTW: I think it is related to this post: Re: code completion settings do not take effect., it is related to ccmanager refactoring.
oBFusCATed:
--- Quote from: oBFusCATed on November 02, 2014, 12:31:21 pm ---This is not a crash, I've just stopped it to see what is doing.
It doesn't crash but what happens is probably that it enters an infinite loop of macro expansion.
I'll try to see if this is related to a single project or the order of evaluation of project breaks it.
--- End quote ---
@ollydbg: Can you guide me where to add logging, so I can try which file causes the problem?
I have multiple projects in a workspace and it is not a single project that causes it :(
I've in fact found the to projects that cause the problem and it is 100% reproducible. And of course I cannot share them. :(
edit: rev 9855 doesn't exhibit the same problem.
ollydbg:
--- Quote from: oBFusCATed on November 03, 2014, 12:11:11 pm ---
--- Quote from: oBFusCATed on November 02, 2014, 12:31:21 pm ---This is not a crash, I've just stopped it to see what is doing.
It doesn't crash but what happens is probably that it enters an infinite loop of macro expansion.
I'll try to see if this is related to a single project or the order of evaluation of project breaks it.
--- End quote ---
@ollydbg: Can you guide me where to add logging, so I can try which file causes the problem?
I have multiple projects in a workspace and it is not a single project that causes it :(
I've in fact found the to projects that cause the problem and it is 100% reproducible. And of course I cannot share them. :(
--- End quote ---
Look at the file Parserthread.cpp, there is a line
--- Code: ---#define CC_PARSERTHREAD_DEBUG_OUTPUT 0
--- End code ---
You can change it to
--- Code: ---#define CC_PARSERTHREAD_DEBUG_OUTPUT 1
--- End code ---
Now, you enable the log message in Parserthread.cpp.
The log messages are default to go in the "Code::Blocks Debug log" panel if you pass "--debug-log" when C::B started, you can redirect them to a file by using some option like:"--debug-log-to-file". Maybe, if you don't pass those options, the debug log messages will be shown in the terminal under Linux.
You can also enable the log message in Parser.cpp(by setting CC_PARSER_DEBUG_OUTPUT to 1) and Tokenizer.cpp(by setting CC_TOKENIZER_DEBUG_OUTPUT to 1) if you still don't find hang reason, but mostly I think only log messages in Parserthread.cpp is enough.
--- Quote ---edit: rev 9855 doesn't exhibit the same problem.
--- End quote ---
I will exam all the related changed after this revision.
oBFusCATed:
@ollydbg: I've done some bisecting and r9931 seems to be the last working revision. r9932 is broken.
scarphin:
My keyboard shortcuts for 'debugging windows' (namely 'alt-shift-x' where x is a digit between 0 and 9) doesn't work after I load a project. Although they are unchanged in the 'cbKeyBinder10.ini', they are not listed in settings->editor->keyboard shortcuts-> corresponding entries nor do they work. Even when I load a modified codeblocks.cbp project file, 'cbKeyBinder10.ini' changes with all the targets added to the file and 'debugging windows' shortcuts gone. I attached a zip containing 2 'cbkeybinder10.ini' files, one before any project loaded and one after codeblocks.cbp loaded. Also what is the .bak file used for?
Btw is there a way to prevent editor from editing while debugging? I often find myself trying to edit the code during a debugging session which is very frustrating. ;)
Win7 x64 SP1
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version