avrmcu & avrserialterm moved to the main module
I think so, because C::B (17.12 release) crashes quite often in particular after I experirnce a slow-down. However, I didn't notice crashes (nor slow-down) on the trunk build, where the symbol browser is disabled completelly.
Right, I also like git. Is it Ok if I will create a PR to your github repo?
Sure! And my feeling it is responsible also for memory corruption and weird behaviour described here. I want try to fix it, using fork of https://github.com/obfuscated/codeblocks_sf ,as bluehazzard adviced. If it would be successfull, can I than attach my future patch to this ticket?
Hello ollydbg! I'm using tdm-gcc v 5.1 distributed in bundle with latest Code::Blocks 17.12. Looks like it already should be considered outdated to build CodeBlocks itself? The size of sdk_precomp.h.gch is about 140M.
I can try to do it, but for that I will ask you to grant me a write access to the C::B development repository to be able to create my own branch of code, because working with such a huge projects is a pain without a source code version control.
I will build codeblocks with debug symbols and try, but till now I didn't noticed the slowness issue with the trunk version built for wx3.1.1.
Hurray! I been able to build the codeblocks trunk using CodeBlocks_wx31.cbp project with wx3.1.1. I only had to disable sdk_precomp.h and sdk.h precompiling for that. Now I can confirm that CC-settings persistence problem disappeared in the trunk version, at least for wx3.x builds. But .. this version lacks the symbol browser pannel altogether! Corresponding View manu item still exists, but it says: "The symbol browser is disabled in wx3.x builds. We've done this because it causes crashes." Have...